-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NTLM HTTP Auth doesn't work (wrong negotiation implementation)? #1
Comments
Negotiate and NTLM are different authentication methods. Negotiate can turn out to be NTLM in the end, but it can also be Kerberos. Anyways. This lib was a very minimal implementation to get WinRM working with the default settings on Azure. (See https://github.com/masterzen/winrm#pluggable-authentication-example-negotiatentlm-authentication) |
Oh and sorry for not paying attention to this repo for a couple of months... |
Hey, I still think there's an issue in the negotiator code. Before |
I only recently learned that one was to supposed to drain connections for proper connection reuse. I'll take a stab at it... |
I'm extra dense today. Do you guys have a fully working example of this thing? The code above does not seem to work for me. |
This is the only place we use it: |
@paulmey I'm not really up on the whole NTLM ecosystem, but what I'm seeing in this library is looking for response headers like UPDATE: I cleaned up my hack a bit, if you would like me to pull request it back in let me know. |
@SleepyBrett, cool that you got it to work. The docs on this protocol are pretty 'light'. PR's are always welcome, especially if they make this lib usable in more cases! Thanks in advance! |
Hi, I think there are few issues with the negotiator. Here's roughly how I'm trying to use your library:
This code doesn't work. It panics with a nil pointer de-reference and after fixing that in negotiator.go, it doesn't correctly authenticate. After making the changes in this diff it works as expected. What do you think?
The text was updated successfully, but these errors were encountered: