You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wanted to give a heads up to save debugging time for anyone getting 401 Unauthorized response when using valid credentials.
In readme it says:
Transport: &httpntlm.NtlmTransport{
Domain: "mydomain", <--- line in question
User: "testuser",
Password: "fish",
...
When I specify domain (like Domain: "my-domain-here",) I receive status code 401. But when I leave it as an empty string (like Domain: "",) I pass authorization. I used same credentials and request URL both times, via HTTPS.
I don't know why it is so, but, well, it is. I'm not all that familiar with NTLM, so maybe I'm just missing something.
If anyone can provide useful info on the subject - please do so.
p.s. I thank the contributors for the library!
The text was updated successfully, but these errors were encountered:
I know this is a year late response, but figured i'd at least point out that the fact that the domain here is not the full "domain" , but rather the TLD for the AD domain you are working with. If you give it something like a hostname or subdomain its going to fail as it used the domain in the challenge request as seen here: https://github.com/vadimi/go-ntlm/blob/main/ntlm/ntlmv2.go#L352
Hello!
Just wanted to give a heads up to save debugging time for anyone getting
401 Unauthorized
response when using valid credentials.In readme it says:
When I specify domain (like
Domain: "my-domain-here",
) I receive status code 401. But when I leave it as an empty string (likeDomain: "",
) I pass authorization. I used same credentials and request URL both times, via HTTPS.I don't know why it is so, but, well, it is. I'm not all that familiar with NTLM, so maybe I'm just missing something.
If anyone can provide useful info on the subject - please do so.
p.s. I thank the contributors for the library!
The text was updated successfully, but these errors were encountered: