[New] LDAP: Use variables in User_Data_FieldMap for name mapping #6921
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
rodrigok
approved these changes
May 17, 2017
|
@bbrauns Awesome addition, thanks. Can you open another PR improving the message bellow the field to explain this new option? Thanks |
|
I will do so. Thx for merging 😃 |
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.
@RocketChat/core
This refers to #6172. A lot of ldap backends do not have a single attribut with the users name, but rather a combination of multiple. This PR makes it possible to use variables in the ldap userdata mapping as seen in the screenshot below. The variables will be replaced with the actual ldap values on ldap user sync.