NTLM Authorization on Rest Service Provider
Now one difference is that uses an OAUTH token vs NTLM authentication. You’ll need that NTLM token (which isn’t a plain text user/password) however SC doesn’t have that capability yet. You would just have to “know it” and enter it there the same as the OAUTH token.
So how do you find it?
You could use a tool like Postman. Postman allows you to enter several credential types including NTLM.
Then when it makes a call to the web service, it converts the creds entered into a proper authorization header.
Once you get that value from Postman, you would just copy it into the field in SmartConnect.
If you are able to find it in Postman for some reason, you could use a tool like Fiddler (www.fiddler2.com) which would trace all calls out to the web service. It WILL be able to capture everything sent including the authorization.
I have tried this and it does not seem to work, I still get 401 Unauthorized
If this was correct, it should be possible for insomnia to have a Header with the Authorization and the NTLM XXXXXX without authorization and it should work, beacuse it doesn’t seem to to me.
I believe there must be some sort of copy protection or something because every time I run it in Postman the authorization changes
It could also be that it is because NTLM sends back a 401 and expects another response and smartconnect doesn’t recognize this. http://davenport.sourceforge.net/ntlm.html#ntlmHttpAuthentication
If you would like to submit an answer or comment, please sign in to the eOne portal.