Don't force TLS bind if not using SSL. #61
Merged
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 code in the
authenticate()
method does:The explicit setting of
auto_bind
to beldap3.AUTO_BIND_TLS_BEFORE_BIND
appears to be wrong because it is forcing TLS negotiation even ifuse_ssl
option wasFalse
.When not using SSL, this results in the error:
because it is perhaps triggering TLS connection against LDAP port 389, or may be because LDAPS port 636 is not working.
This PR changes the code to:
so that TLS binding is only requested if
use_ssl
isTrue
.This eliminates the exception and is believed not to affect SSL behaviour, although didn't have a LDAP with working LDAPS port to test.
It is amending what was originally added for this in #46