-
Notifications
You must be signed in to change notification settings - Fork 81
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
Change of email process security updates #1140
Comments
I have solved "The confirmation email sent to the new email address should not include the username for security purposes." part of problem. |
Hi @amplifi @oliverroick |
Hi @Rjain111 thanks for your interest in fixing this issue. Fully addressing this issue requires some design work and planning upfront, which haven't completed yet. That's why we haven't tagged this issue for as first-contribution friendly. |
Steps to reproduce the error
Go to Edit Profile and change the email address on a user account
Actual behavior
The user is not prompted to verify their password to confirm identity before submitting change of email address.
A confirmation email is sent to the new email address, which includes the account username.
The new email address is applied to the account upon form submission (before it is verified via the link in the confirmation email). This means anyone who accesses a user account can change the email address and the user would not be alerted, or the user could change to an incorrect/invalid email address and have no way to recover their account.
Expected behavior
The confirmation email sent to the new email address should not include the username for security purposes.
The user's email address in the database should not be updated until after the user clicks the verification link in the confirmation email.
A separate notification email should also be sent to the old address. In the event of unauthorized changes, this will alert the user to the change.
The notification email to the old email address should advise the user to let us know immediately if this change was not authorized, and provide them with a contact method.
The text was updated successfully, but these errors were encountered: