-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Case sensitive emails #2698
Comments
A quick fix, is to update the records in users collection. Here is a sample script which can be executed in mongo shell.
Verifying after executing the above script.
|
Add the above code to migration script |
Removed from 0.11.2 milestone as it has been agreed that this is out of scope. Anyone upgrading from older versions can use the information on this issue to upgrade using the Mongo script |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've discovered after upgrading a client from AAT 0.10.5 to AAT 0.11.1 that the majority of their users were no longer able to log in to the Authoring Tool.
After spending an hour head-scratching what the issue was, I noticed that some users had capitalised letters in their email addresses and others didn't. It appears that those users weren't able to log in.
It appears that if you try to create new users, after upgrading with capitalised letters, it automatically replaces the capitalised letters for non-capitalised, preventing this happening for new AAT installs, but the upgrade script didn't account for this and these users were unable to access the Authoring Tool until the administrator changed their names manually.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: