Incident restore: an option to reset every second factor #1160

Open
opened 2026-11-11 15:37:53 +00:00 by Cordy · 0 comments
Owner

Follow-up from #1046. After a suspected compromise of the key file or the state store, an administrator may want to reset every two-step sign-in record at once (people set it up again at their next sign-in, the requirement's date restarts). Today the reset is per account. Decide where it lives (the #1104 incident restore checklist or Users & access), the confirmation, the mails, the audit, and the multi-instance rollout (daily job lease).

Follow-up from #1046. After a suspected compromise of the key file or the state store, an administrator may want to reset every two-step sign-in record at once (people set it up again at their next sign-in, the requirement's date restarts). Today the reset is per account. Decide where it lives (the #1104 incident restore checklist or Users & access), the confirmation, the mails, the audit, and the multi-instance rollout (daily job lease).
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1160
No description provided.