Recover an account that lost every factor
Two of your organization's administrators issue a one-time recovery pass; the person uses it to add a new passkey and signs in with that. Nobody ever learns their credentials, and there is no break-glass account.
When someone at your verified domain has lost everything they sign in with (phone, security key, laptop), two of your organization's owners or admins get them back in. The person never receives a password from anyone: they receive a recovery pass, which only lets them add a new passkey.
Recovery works for accounts your organization manages.
Recover someone
- An owner or admin opens the person under Settings → Organization → Members, and in the Account section chooses Start recovery.
- A different owner or admin opens the same person and approves it. The person who started recovery cannot approve it. A request waits up to 24 hours; either administrator can cancel it.
- Approving signs the person out everywhere and shows a recovery pass once. It is valid for one hour. Give it to the person over a channel other than the one they asked on: if they asked by email, read it out on a call.
- The person opens
/auth/recover-with-passon your Scrydon address, enters their work email and the pass, and adds a passkey on their device. - They sign in with that passkey, the normal way, under your sign-in policy.
Every owner and admin of your organization is notified when a pass is issued and when it is used. Both steps are in the Audit Log.
If the old phone or key may be in someone else's hands, also reset the account's credentials so only the new passkey works.
The pass
- It works once, for one hour, and only to add a passkey. It never signs anyone in by itself.
- Five wrong tries destroy it. A wrong address, a wrong pass and an expired pass all get the same answer.
- Scrydon keeps only a fingerprint of it. If it is lost, start again.
Two administrators, always
Recovery needs two people, so an organization with a verified domain keeps at least two owners or admins who can sign in. Scrydon refuses to remove, demote, suspend or offboard an administrator, or let one leave, when that would leave fewer than two. If your organization has only one, the domains settings (Settings → Platform → Identity → Domains) show a warning: add a second administrator.
When every administrator is locked out
Nobody in your organization can then start recovery. Contact the operator of your Scrydon deployment through a channel they can verify. Two of their operators issue a recovery pass to one of your administrators, who then recovers everyone else. Every owner and admin is notified when they do; if you did not ask for it, contact the operator at once.
There is no break-glass account that skips your sign-in policy. That is deliberate: such an account is the one an attacker goes after first.
API
Under the authentication service. The first four are for the session's active organization; the last two are public and take no session.
| Method and path | Does |
|---|---|
GET /sso-extensions/managed-accounts/:userId/recovery | { userId, request, pass } |
POST /sso-extensions/managed-accounts/:userId/recovery/request | start recovery |
POST /sso-extensions/managed-accounts/:userId/recovery/approve | approve: { pass, expiresAt }, once |
POST /sso-extensions/managed-accounts/:userId/recovery/cancel | cancel the request or the pass |
POST /sso-extensions/account-recovery/passkey/options | { email, pass } → passkey options |
POST /sso-extensions/account-recovery/passkey/verify | { email, pass, response } → the passkey is added |
Errors carry a code: recovery_not_pending (404), recovery_self_approval,
recovery_needs_second_admin and admin_floor (403),
recovery_pass_invalid, recovery_challenge_expired and
recovery_passkey_unverified (400), and recovery_not_enabled (404) when the
deployment has recovery off. The public routes answer 429 after 5 requests a
minute.
Other alerts
Your owners and admins are also notified when single sign-on enforcement is switched off, or a provider that enforced it is deleted.
Microsoft 365
If your domain signs in to Microsoft 365 through Scrydon, someone locked out
of Scrydon is locked out of Microsoft 365 too. Keep Microsoft's own
emergency access accounts on your onmicrosoft.com domain, not on the domain
you federate, so you can still reach Microsoft 365 if Scrydon itself is
unavailable.