Why Services Still Require TOTP Even After Enabling Passkeys
The transition to FIDO2 / WebAuthn is multi-year. Here is why services keep TOTP fallbacks and how to stay secure.
Last updated: November 15, 2026
Author: Perry Lei
Reviewed: November 15, 2026 by TOTPBOX Security Review
Passkeys represent the future of phishing-resistant authentication, but until platform ecosystems achieve universal cross-device parity, TOTP remains the primary operational safety net across the internet.
1. Cross-platform & legacy browser gaps
While Apple, Google, and Microsoft support synced passkeys in their respective ecosystems, cross-ecosystem synchronization remains fragmented. When logging in from a corporate workstation, a Linux desktop, or an older browser without WebAuthn Level 2 support, services fall back to RFC 6238 TOTP to prevent permanent lockout.
2. Developer tooling and CLI authentication
Many critical platforms (such as GitHub, AWS, and Cloudflare) require two-factor authentication for automated workflows, terminal commands, and Git operations over SSH or HTTPS. Because headless terminal sessions cannot easily invoke native OS biometric dialogs, services retain TOTP as a mandatory secondary authentication mechanism.
- Command-line interfaces (CLIs) and API token generation
- SSH key approval and remote bastion authentication
- Git credential helpers in remote server environments
- Automated deployment agents and CI/CD pipelines
3. Account recovery workflows
If a user loses all hardware security keys or loses access to their platform keychain, services require alternative proof of ownership. TOTP paired with single-use recovery codes provides a deterministic recovery path without relying on insecure SMS verification.
4. How TOTPBOX manages the dual posture
TOTPBOX is designed specifically for this transition era. Instead of forcing you to abandon TOTP before services are ready, TOTPBOX:
- Stores your TOTP secrets in an on-device AES-256-GCM encrypted vault
- Identifies which accounts support Passkeys via the Auth Health Dashboard
- Provides step-by-step guidance to upgrade accounts as services roll out FIDO2
- Retains recovery codes securely so fallback paths remain accessible