Without bind_dn_template, any password is authenticated successfully!
See original GitHub issueWhen initially configuring ldapauthenticator, I accidentally left bind_dn_template out of my config. When I tested it, I noticed it was authenticating me even with incorrect passwords!
This seems very dangerous. Although this parameter is required, authentication should probably always fail rather than always succeeding (or jupyter hub should simply refuse to start if required values are missing).
This happened when I had the following config vars set: server_address, lookup_dn, user_search_base, user_attribute
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10
Top Results From Across the Web
password is mandatory in simple bind - Stack Overflow
I am trying to set up authentication with flask and ldap3 . For this I have a global_authentication.py, a main.py in which I...
Read more >Unable to bind or log into LDAP using specific credentials
After spending an hour attempting to resolve it without success, i simply created an ldap user account to use with LDAP.
Read more >Resolve a Bind Error in Active Directory Authentication
For the Bind to be successful, the full and correct Distinguished Name (DN) or Searching User UPN must appear in the DN of...
Read more >Authentication - CodeChecker
Users are authenticated if any authentication method successfully authenticates ... if not set bind with the login credentials will be attempted. password.
Read more >Configuring LDAP remote authentication for Active Directory
The Password and Confirm entries must match. Note: The Bind and User Template options are mutually exclusive. You can define one setting or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This sounds like a bug. I’ll check if I can reproduce to confirm…
@ermakovpetr - yes, I think the functionality in #88 is orthogonal to that in #95