Skip to content
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

[TRI-2630] Logging in with the same email but different case creates a new account #1144

Open
matt-aitken opened this issue Jun 2, 2024 · 4 comments · May be fixed by #1239
Open

[TRI-2630] Logging in with the same email but different case creates a new account #1144

matt-aitken opened this issue Jun 2, 2024 · 4 comments · May be fixed by #1239
Assignees

Comments

@matt-aitken
Copy link
Member

matt-aitken commented Jun 2, 2024

If you login with [email protected] and [email protected] you will create two accounts.

From SyncLinear.com | TRI-2630

@matt-aitken matt-aitken changed the title Logging in with the same email but different case creates a new account [TRI-2630] Logging in with the same email but different case creates a new account Jun 2, 2024
@hunxjunedo
Copy link

@matt-aitken kindly assign this issue to me, would like to contribute.

@matt-aitken
Copy link
Member Author

[email protected] and [email protected] can be treated as equivalent because DNS specifies that domain names are to be compared in a case-insensitive manner. But the same is not true for the user/mailbox part of an address, that should actually be case sensitive so we should create multiple accounts for those.

image

@matt-aitken
Copy link
Member Author

@matt-aitken
Copy link
Member Author

@hunxjunedo I've assigned this to you 👍

I've also added some more comments above about what exactly should cause a duplicate and what shouldn't

@Kritik-J Kritik-J linked a pull request Jul 29, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants