Add support for Microsoft Active Directory in LDAP authentication #346
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current schema / format of the
dnthat works with OpenLDAP servers does not always work when trying to use an Active Directory domain controller as an LDAP authentication server.In testing it seems more reliable to authentication using a username of
DOMAIN\\usernamerather than trying to guess what thednis being used at a given site. The problem is that the username is not always part of thednfor AD, but using the username and domain name always seems to work.I've tested the code in this PR at BNL using the onsite Active Directory Domain Controllers (and also using a DUO MFA proxy server). I have not tested against Azure AD.