Skip to content
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

Trouble with NTLM Proxy Authentication #10

Closed
eabovsky opened this issue Jan 13, 2018 · 1 comment
Closed

Trouble with NTLM Proxy Authentication #10

eabovsky opened this issue Jan 13, 2018 · 1 comment

Comments

@eabovsky
Copy link

I've been trying to implement this library to perform NTLM Proxy Authentication, and am running into a peculiar issue.

The environment setup is:

  1. Both the client machine and the proxy are on the same domain.
  2. The proxy supports Kerberos, NTLM, and Negotiate.

If negotiate is used and selects Kerberos, everything works fine.

However, if I try to force NTLM as the package, the final token gets rejected by the proxy. When testing the code at other sites where NTLM is the only supported option, the handshake also fails in the same way.

My gut instinct is something is wrong with the credential handle or the crypto functions for generating the 3rd token. When I loaded up a token analysis tool, all of the flags and target information looks identical to other apps' tokens which do seem to work.

@eabovsky
Copy link
Author

Figured it out.

The problem was that the same socket connection must stay open for the challenge/response calls.

@antiduh antiduh closed this as completed Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants