Fix a regression wherein users with historical usernames containing capital letters can't log in #168
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.
Introduced in #163, which attempted to allow users to authenticate with LDAP usernames containing capital letters by lowercasing the username before interacting with Synapse. This then broke logins for users with historical usernames containing uppercase letters, as the login process created an access token based on the lowercased username, which didn't actually exist. This PR fixes this by only lowercasing the username if synapse is going to create a new account for the user, and using the value returned by
check_user_exists
as the canonical username.