Repository navigation
Conversation
Contributor
|
Closing this as it's out of date, missing a linked issue, and missing tests. If still relevant please consider creating an issue and sending a new PR. |
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
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.
Allow for templating of default value when using LDAP attribute mappers. This is useful when creating LDAP accounts with attributes such as
homeDirectorywhich can, depending on the use case, be derived from the username using a template such as/home/${attr.username}. This templating mechanism uses a similar format to that used in the Vault SPI and allows for usage of any already defined user-attribute as part of an LDAP default value string.