Reference
Two-step methods
The second steps Sovrain accepts at sign-in - authenticator apps, security keys, passkeys and backup codes - with their limits.
A second step is asked for after the password. Sovrain accepts four methods. Each person manages their own on
Profile › Security (/profile/security). Whether a second step is required is set by the organization’s admins:
Require two-step sign-in. Background:
About two-step sign-in.
| Method | Card on Profile › Security | Per account | amr in OpenID Connect |
|---|---|---|---|
| Authenticator app | Authenticator apps | up to 5 | ["pwd", "otp", "mfa"] |
| Security key | Passkeys and security keys | up to 10 security keys and passkeys together | ["pwd", "hwk", "mfa"] |
| Passkey | Passkeys and security keys | (shared with security keys) | ["pwd", "swk", "mfa"] when synced, ["pwd", "hwk", "mfa"] when not |
| Backup codes | Backup codes | one set of 10 | ["pwd", "otp", "mfa"] |
At sign-in, the methods are offered strongest first: passkey or security key, then authenticator app, then backup code. Use another method shows the others.
Authenticator app
| Item | Value |
|---|---|
| Standard | TOTP (RFC 6238) |
| Algorithm | HMAC-SHA1 |
| Digits | 6 |
| Period | 30 seconds |
| Tolerance | One period before and after |
| Secret | 20 bytes, shown as a QR code and as a key to type |
| Reuse | A code that was accepted once is not accepted again |
| Name | At most 60 characters. Default Authenticator. |
| Issuer shown in the app | At most 64 characters |
| Per account | 5 |
Security keys and passkeys
Both use WebAuthn. A security key is a physical key, such as a YubiKey. A passkey lives on a device, a phone or a password manager.
| Item | Value |
|---|---|
| Algorithms | ES256, EdDSA, RS256 (RSA keys of 2048 to 8192 bits) |
| Attestation | none |
| User verification | preferred |
| Resident key | discouraged; preferred for a passkey on Android |
| Time to complete | 5 minutes |
| Per account | 10, security keys and passkeys together |
| Synced or not | Read from the key’s backup flag. A synced passkey reports swk in amr, any other key hwk. |
| Bound to | The address the key was added at. After the organization moves to a custom domain, keys added at the old address stop working and must be added again. |
Backup codes
| Item | Value |
|---|---|
| Codes per set | 10 |
| Format | 10 characters, shown as XXXXX-XXXXX |
| Use | Each code works once |
| Shown | Once, when the set is generated. Copy and Download (backup-codes.txt) are offered. |
| Confirmation | After saving, the person types one code to confirm. The code stays usable. |
| Warning | At 3 codes or fewer left |
| New set | Generate a new set replaces the old set. Needs a sign-in less than 5 minutes old and ends the person’s other sessions. |
Rules for every method
| Item | Value |
|---|---|
| Wrong codes or keys per sign-in | 5 tries within 5 minutes, then the sign-in starts again |
| Wrong second steps per account | 10 per hour, shared by sign-in, password reset and delegation |
| Wrong second steps per client address | 60 per 15 minutes |
| Time to complete the step | 5 minutes after the password |
| Adding a method | Needs a sign-in less than 5 minutes old. The first method ends the person’s other sessions and shows the backup codes. |
| Removing a method | Remove a second factor. Needs a sign-in less than 5 minutes old. Refused when the organization requires two-step sign-in and it is the last method. |
| Admin actions | An admin can remove one method or reset all of them from the user’s page; the person is signed out and, with a verified address, receives an email. Only an owner can do this for another owner or administrator. |
Lost every method
When no method works, two-step sign-in is reset:
- by the person, with Lost access to two-step sign-in?, only when the organization turned on Email as a backup factor (off by default) and the account has a verified email. The person confirms with the password and a link from the email, opened in the same browser, and sets up an authenticator app again. Security keys and passkeys cannot be set up on that page.
- otherwise by an administrator, with Reset two-step on the user’s page.
Steps: Recover lost two-step sign-in.
Not supported
- Sign-in without a password (passwordless), with a passkey or otherwise.
- Codes by SMS, by phone call or by email as a second step.
- Push notifications to a phone app.
- TOTP with SHA-256 or SHA-512, 8 digits or another period for sign-in. (The password manager can store such codes for other sites.)