Authentication and MFA
These components deal with how people prove who they are — reading their registered methods, removing ones that no longer apply, and getting someone back in when their second factor is unavailable.
List Authentication Methods
Returns the sign-in methods a user has registered: authenticator app, phone, FIDO2 security key, Windows Hello and so on.
Useful both for support work and for checking coverage before you tighten a policy.
Delete Authentication Method
Removes one registered method from a user.
The everyday case is a device swap. Someone gets a new phone, and the authenticator registration on the old one should not stay valid — particularly if the old device is being passed on or returned.
Create Temporary Access Pass
Creates a time-limited, single-use code that lets a user sign in without a password and register their authentication methods from scratch.
This solves two situations that are otherwise awkward:
Onboarding. A new starter has no password and no registered second factor. The access pass gets them to the point where they can set up both themselves.
Lost or replaced phone. The user cannot complete their second factor and therefore cannot fix their second factor. The access pass breaks that loop.
Validity is set in minutes, and you can decide whether the pass may only be used once and when it becomes valid.
The pass is returned only in this one response and cannot be retrieved afterwards.
Send it on within the same flow run. For onboarding, sending it to the line manager works better than the new mailbox, which the person cannot reach yet.
Was this helpful?