-
Notifications
You must be signed in to change notification settings - Fork 38
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
MS Active Directory user credential validation failure #54
Comments
Hi @bridnic there are numerous reasons why an auth failure might be returned from the library. I think the best way to debug this from here would be to enable debug logging and see if we can narrow down the path the request is taking inside the library. You can enable debug logging by setting the level of the library like so: import logging
logging.getLogger('flask_ldap3_login').setLevel(logging.DEBUG)
... Let me know what output you get from this when testing with your code. |
Hi @nickw444 Here is the output of the debugging:
It's probably worth noting that I'm running Python 2.7.5 and so to allow the debug to run correctly, I had to add the line below to the script.
|
Hi @bridnic, did you ever manage to solve the issue you were having? Also, just a side note: after a long internal debate, I have made the difficult decision that I will no longer be actively maintaining this repo. I am now in the process of finding a new maintainer - if this is something that may interest you, you can find more details in the README |
Hi @bridnic, did you solve this? My guess is that cn of the user object doesn't have the |
same as me |
Same problem here as well. Anyone has been able to figure this out? Interestingly the event logs show NTLM auth successful for the bind. @bridnic I believe your search filte rlooks wrong. When I use ldp.exe on Windows with (&(objectclass=user)(cn=domain\test-user)) it gives error. It works with (&(objectclass=user)(cn=test-user)) |
User credential validation against MS Active Directory (via NTLM) appears to always fail. From performing an element of troubleshooting, the bind is successful and I can see that the initial search for the user (needing to be validated) succeeds. However, the credential validation always fails with the following error:
No handlers could be found for logger "flask_ldap3_login"
AuthenticationResponseStatus.fail
Below is the configuration that is being used in the test script.
The text was updated successfully, but these errors were encountered: