question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fail to authenticate via NTLM

See original GitHub issue
  1. Newman Version: 3.7.5
  2. OS details (type, version, and architecture): Win 7 Enterprise SP1 64-bit
  3. Are you using Newman as a library, or via the CLI?: CLI
  4. Did you encounter this recently, or has this bug always been there: n/a
  5. Expected behavior: newman should support NTLM auth
  6. Command / script used to run Newman: see below in test steps
  7. Sample collection, and auxilliary files (minus the sensitive details): n/a
  8. Screenshots (if applicable): n/a
  9. Node version: 6.9.4

Steps to reproduce:

  1. Have service with NTLM auth
  2. Create postman collection with GET endpoint to that service
  3. Setup test that endpoint with valid auth credentials (see collection example)
  4. Run test
newman run <COLLECTION URL/FILE PATH> --color --environment <ENV URL/FILE PATH> --reporters junit,cli,html --reporter-junit-export test_junit_format.xml --reporter-html-export test_html_format.html

Actual result: request fails with Auth error

Collection example

{
	"variables": [],
	"info": {
		"name": "-----",
		"_postman_id": "-----",
		"description": "",
		"schema": "https://schema.getpostman.com/json/collection/v2.0.0/collection.json"
	},
	"item": [
		{
			"name": "Setup",
			"description": "----",
			"item": [
				{
					"name": "----",
					"event": [
						{
							"listen": "test",
							"script": {
								"type": "text/javascript",
								"exec": [
									""
								]
							}
						}
					],
					"request": {
						"url": {
							"raw": "----",
							"protocol": "https",
							"host": [
								"----",
								"---",
								"----"
							],
							"auth": {
								"user": "----",
								"password": "-----"
							},
							"path": [
								"-",
								"-",
								"-",
								"-"
							],
							"query": [
								{
									"key": "s-",
									"value": "-",
									"equals": true,
									"description": ""
								}
							],
							"variable": []
						},
						"method": "GET",
						"header": [],
						"body": {},
						"description": "-"
					},
					"response": []
				}
			]
		}
	]

Thanks

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
rathodamolcommented, Dec 20, 2018

Is there any update on the issue on NTLM auth using the newman cli ? I am still stuck 😃

0reactions
johan-v-rcommented, Nov 17, 2017

Hi All

The NTLM Authentication (Beta) in postman currently works fine from my machine. However I’m still having issues executing this with newman cli.

I’m running node v8.1.3 & newman v3.8.3

After exporting from Postman Collection v2.1, my request looks like:

{
"name": "Index",
"event": [
	{
		"listen": "test",
		"script": {
			"type": "text/javascript",
			"exec": [
				"pm.test(\"Status code is 200\", function () {",
				"    pm.response.to.have.status(200);",
				"});",
				"",
				"pm.test(\"Body matches string\", function () {",
				"    pm.expect(pm.response.text()).to.include(\"test\");",
				"});"
			]
		}
	}
],
"request": {
	"auth": {
		"type": "ntlm",
		"ntlm": [
			{
				"key": "username",
				"value": "user",
				"type": "string"
			},
			{
				"key": "password",
				"value": "xxxxxxx",
				"type": "string"
			},
			{
				"key": "domain",
				"value": "",
				"type": "string"
			},
			{
				"key": "workstation",
				"value": "",
				"type": "string"
			},
			{
				"key": "disableRetryRequest",
				"value": false,
				"type": "boolean"
			}
		]
	},
	"method": "GET",
	"header": [],
	"body": {},
	"url": {
		"raw": "http://foo.bar.net",
		"protocol": "http",
		"host": [
			"foo",
			"bar",
			"net"
		]
	},
	"description": ""
},
"response": []

Any help would be appreciated.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Authentication failure from non-Windows NTLM or Kerberos ...
This article provides a solution to several authentication failure issues in which NTLM and Kerberos servers can't authenticate Windows 7 ...
Read more >
Restricted users fail to authenticate with NTLM - Forcepoint
To work around the problem, in your Active Directory add a workstation named "TMP" and include it in the set of workstations available...
Read more >
How to troubleshoot the NTLM(HTTP 401) authentication
1. Ensure that NetBIOS Name Resolution is enabled on the Domain Controller to which the Web Gateway is sending the NTLM requests. ·...
Read more >
Resolve failing SMB Client Connections with NTLM ...
Adjust NTLM Authentication Level · Restart client computer for changes to take effect · Verify the issue is resolved by attempting to mount...
Read more >
NTLM SSO Authentication Failure - MailArchiva Online Help
Using Internet Explorer, try logging into Active Directory using the standard MailArchiva login page. To do this, enter the equivalent of http://localhost:8090/ ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found