[6.x.x] Address issues in the LDAP Security Realm #168
Conversation
This file contains hidden or 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
…een handled by the LDAP security module for some time
… previously: not being able to authenticate, not being able to retrieve a group, missing metadata attributes, and a number of issues with qualified and unqualified principal names. Closes #141
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.
Backport of #167
This fixes a number of issues in the LDAP Security Realm module, including:
StackOverflowErrorSecurityManager#getGroup(String)It also removes the defunct and unusable Active Directory Security Realm module, as its functionality can be achieved with by using the LDAP Security Realm module instead.
In addition it adds a set of Integration Tests for the LDAP Security Realm that tests the realm against an embedded Apache Directory Server.
Closes #141