This repository has been archived by the owner on May 17, 2021. It is now read-only.
Use token getCrendentials instead user getPassword. Fix #76
#88
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
The correct way of verify user authentication is binding again against the LDAP backend with the original credentials used on login. This is the token `getCredentials()` method.
|
@Saaha Could you check if this patch fix the issue with the credentials? |
Maks3w
added a commit
that referenced
this pull request
Apr 29, 2015
Use token `getCrendentials` instead user `getPassword`. Fix #76
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 correct way of verify user authentication is binding again against the LDAP backend with the original credentials used on login.
This is the token
getCredentials()method.