Check RDN attribute for DN membership #21774
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.
Closes #20718
The PR just returns the groups members whose DN starts with the specified attribute name (for example,
CNfor for groups orUIDfor users). This allows to differentiate entries that are groups or users. Note that they can even be the same (for example in AD, both users and groups usually use CN as the RDN attribute). Checking the code this is already being done although later on (for example when getting the user name here or here or getting the group name here). So no real change in behavior.Tests modified to add a non-existent member that uses a different RDN attribute.