Provide a method for 2-factor self-recovery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
If a user loses/forgets their 2-factor device(s), they will be locked out of their account until they get an admin to unlock it for them. We need to look into self-service options. Some initial ideas:
* Require a user to generate a single OTP 'recovery' token when they first enable the 2-factor feature. When they use it, a new one should be generated before they can proceed further. This may still be prone to people forgetting/losing the token.
* Provide a "help! I lost all my devices!" link which sends a single OTP 'recovery' token to their preferred email address so they can get back into their account. This assumes that their email account isn't compromised as that effectively becomes the weakest link in our chain.
* Provide users the option of registering a mobile phone number as an additional 2-factor device. We could then send them the next OTP token in the sequence by SMS when they request it. This assumes that they weren't using this mobile device as their primary 2-factor device - so, maybe a spare phone or their partner's phone?
Other ideas?
Changed in canonical-identity-provider: | |
milestone: | none → public-rollout |
tags: | added: twofactor |
tags: | added: u1-support |
tags: | added: u1-by-support |
tags: | removed: u1-support |
Use their launchpad GPG key to GPG-encrypt a recovery token to them and send via email?