New — Iris AI drafts your firewall, routing & rate-limit rules. Explore AI features →
Changelog
Security

A second step at sign-in: passkeys, authenticator apps, recovery codes

Ask your users for a passkey or an authenticator app after their password or single sign-on. They set it up themselves and manage it on their account page.

A second step at sign-in: passkeys, authenticator apps, recovery codes

A password, or a Google account, is one thing someone can steal. An app with customer data or admin pages wants a second proof that it's really your user, without that proof written into the app.

Now an endpoint can ask for a second step after the password or single sign-on: a passkey (Face ID, Touch ID, Windows Hello, a security key or a phone) or an authenticator app with a 6-digit code. Once Maya requires it for the console, Dana sees the page above at her next sign-in, after a code we email her.

The confirm Require a second step?: 2 users set one up at their next sign-in, after a code we email them; 3 browsers signed in without a second step sign in again
Before the requirement is saved, the confirm says what changes for the console's users.
The second step page of Dana's account: an authenticator app, a passkey on Mac, 9 recovery codes left, and Add a passkey
Dana manages her second step on her account page. She can add a passkey, remove one or make new recovery codes, and each change asks her to confirm it's her first. Since the console requires a second step, she can't turn it off.
How Maya signs in, on her page in Users: a Google account, and Second step: 2 passkeys, 10 recovery codes left, with Reset
Each user's page shows what they set up. If someone loses their phone and their passkeys, Reset removes them all, and they set up a new second step at their next sign-in.

What changed

  • Require a second step for everyone, in Sign-in under Second step. Before it saves, it says what changes for your users. It works over HTTPS.
  • Users set it up themselves. At their next sign-in, after a 6-digit code we email them, they pick a passkey or an authenticator app. They also get 10 recovery codes, each working once.
  • A setup link for users without an email. Create setup link on their page makes a link that works once, for 1, 3 or 7 days. It's shown once, for you to send them.
  • On their account page. Users add a passkey or the app, remove one, make new recovery codes, or turn the second step off when you don't require it. They get an email when one is added or removed. Without the requirement, users can still add one there.
  • Scripts keep working. Access tokens and API keys aren't asked for a second step. A password sent with each request is refused for users who need one: give those scripts an access token.
  • Providers that ask their own. If your single sign-on provider already asks a second step of everyone, turn on This provider asks its own second step, and its sign-ins skip the endpoint's.
  • Your app can check it. The signed token's mfa claim says how the browser passed: totp, passkey, recovery_code or provider.
  • Wrong codes pause. After too many wrong codes, the user's codes are paused for a while. A passkey keeps working.

Get started

  1. Open the endpoint's Sign-in & access tab, then Sign-in.
  2. Under Second step, turn on Require a second step for everyone, and save.
  3. Read what changes, then click Require.
  4. For a user without an email, open their page in Users and click Create setup link.
  5. Read the docs: Second step and The signed token.

Read the docs

Ask an AI to summarise this page
Deploy
App hosting Edge functions Domains & certificates
Connect
Secure tunnels API gateway Multi-region edge
Protect
Bot protection & challenge WAF & firewall Edge login
Observe & AI
Monitoring Inspector & replay Iris AI MCP server AI Gateway
Developers
Developer tools Docs ngrok policy converter Blog Changelog
Compare
Ngris vs ngrok Ngris vs Cloudflare Tunnel Ngris vs Vercel Ngris vs Netlify Expose localhost guide
More
Solutions Pricing Enterprise Sign in Get Started Free