allow admin to generate a printout with temporary one-time passwords for an user

Bug #911951 reported by Ricardo Kirkner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Won't Fix
Wishlist
Unassigned

Bug Description

User story:

As a SSO admin, I want to be able to generate a sheet of 10 valid tokens for a specific user from their admin profile so that I can provide them with temporary access to their account if they lose/forget their 2nd factor device.

Details:

Add a way for an admin to generate a printout sheet with 10 valid one-time passwords associated to an users account

Related work include:

- generate multiple OTP and associate them to the users account
- invalidate each used password after the first successful login (possibly keep them around with the date they were used)
- indicate the status of the passwords in the user's account detail page (used/unused)
- allow admin to invalidate set of OTP (in case the user lost the printout sheet)

Revision history for this message
Stuart Metcalfe (stuartmetcalfe) wrote :

"(possibly keep them around with the date they were used)"

Remember that OATH/HOTP is a counter/event based OTP, so when a token is used, it automatically invalidates previous sequential tokens (generated with a lower counter value) and, on the other side, going too far ahead (exceeding the counter drift setting) will fail validation. The list of generated tokens should be enumerated and are designed to be entered in sequence. We probably shouldn't display the gen'd tokens after the first time - it should be up to the admin to mail/print/read them for the user at the time of generation.

Changed in canonical-identity-provider:
importance: Undecided → Medium
status: New → Triaged
David Owen (dsowen)
tags: added: kb-feature sp-1
Changed in canonical-identity-provider:
milestone: none → 2-factor-internal-production-ready
David Owen (dsowen)
Changed in canonical-identity-provider:
importance: Medium → Low
Changed in canonical-identity-provider:
milestone: 2-factor-internal-production-ready → 2-factor-post-release-1
Changed in canonical-identity-provider:
milestone: 2-factor-internal-rollout → 2-factor-post-rollout
Revision history for this message
Selene ToyKeeper (toykeeper) wrote :

Depending on how the details work out, this may be relevant for our new-starter processes. Basically, the new employee could receive a sheet of ~50 one-time passwords along with their other new employee materials, which would let them log on until they have another solution configured. This isn't confirmed though, just a possibility.

Changed in canonical-identity-provider:
importance: Low → Wishlist
milestone: 2-factor-post-rollout → none
Daniel Manrique (roadmr)
Changed in canonical-identity-provider:
status: Triaged → Won't Fix
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.