New, LDAPS TLS config options #833
Merged
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.
New,
LDAPS TLS config options:
AUTH_LDAP_TLS_DEMAND
AUTH_LDAP_TLS_CACERTDIR
AUTH_LDAP_TLS_CACERTFILE
AUTH_LDAP_TLS_CERTFILE
AUTH_LDAP_TLS_KEYFILE
It's now possible to use LDAPS with internal certificates or public, with improved security options. By using TLS_DEMAND. Also possible to use AUTH_LDAP_TLS_CERTFILE and AUTH_LDAP_TLS_KEYFILE for client side authentication.
Current support for LDAPS, ldap.OPT_X_TLS_REQUIRE_CERT (TLS equivalent: TLS_REQCERT)
demand:
no certificate provided: quits
bad certificate provided: quits
allow
no certificate provided: continues
bad certificate provided: continues