services: update user's DB entry from LDAP (if needed) #46
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
… full name. Username is assumed non-changing here. Not sure what happens to Taiga/Django if the `username` changes - are all references changed or orphaned?..
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.
Updates the Taiga / Django database entry if LDAP returned different e-mail or full name values.
Before this, for example, if the e-mail value changed in LDAP, logging into Taiga would still only be possible with the old e-mail. If editing e-mail is disabled (e.g. as described here), this means the user has to remember their first-ever login e-mail. And if editing is enabled, then the user would still have to update this manually.
(Username is assumed non-changing here. Not sure what happens to Taiga/Django if the
usernamechanges - are all references changed or orphaned?..)Note: this is not the PR mentioned in issue 37.