New Email Management Functionality Issues

Bug #610184 reported by Julien Funk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Invalid
Medium
Unassigned

Bug Description

Bug Description:
There were a few issues when I tested the new email mgmt functionality.

1. When removing addresses, the system says all addresses are 'unverified' addresses even if they are verified
2. The error message "Unknown confirmation code" is misaligned with the elements of the page, it should be lower see screenshot
3. Able to use an old token-link from an email to verify a new email address

OS: 10.4

Browser: FF3.6

Problem URL: https://login.staging.ubuntu.com/+emails

Steps To Reproduce:
#1 : go to the link above and remove a verified address, you will see the text use the term "unverified" when it asks if you want to delete and when it confirm that you have deleted the email

#2:
a. add a new email to your SSO account
b. instead of verifying with the proper code, put in a defective code and see that the error message is misaligned with the elements of the page (see also screenshot)

#3:
a. add a new email address
b. check your email and see that you have a new token, but do not enter it in yet
c. delete the email and then add the same email a second time
d. check your email to se that you receive a 2nd token, but instead of using that token, go to the first email and click the link provided in that email - you will get a confirmed email address using a token that should have expired...

Revision history for this message
Julien Funk (jaboing) wrote :
Revision history for this message
Łukasz Czyżykowski (lukasz-czyzykowski) wrote :

Created separate for each of those issues:
1. Bug #61215 - Wrong flash message when removing verified email
2. Bug #661216 - Misaligned error message when wrong confirmation code is entered
3a. Bug #661232 - Add expiring authtokens to cleanup command
3b. Bug #661233 - When removing unverified email address also remove authtoken for that email

Marking this one as Invalid.

Changed in canonical-identity-provider:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.