TOTP & HOTP

TOTP (tidsbasert engangspassord, RFC 6238) og HOTP (HMAC-basert engangspassord, RFC 4226) er de to RFC-ene som enhver 2FA-registrerings-QR implementerer. Det kodede URI-skjemaet otpauth:// er Google Authenticators de facto-standard, universelt i alle større autentiseringsapper.

Hva det er

En 2FA-registrerings-QR er en URL i otpauth://-skjemaet som bærer den delte hemmeligheten og identifiserende metadata. Format:

otpauth://TYPE/LABEL?secret=SECRET&issuer=ISSUER&algorithm=ALG&digits=N&period=SEC

• TYPE, totp (time-based) or hotp (counter-based).
• LABEL, Issuer:Account, URL-encoded. Example: GitHub:alice@example.com.
• secret, the shared key, Base32-encoded (RFC 4648 §6 alphabet: A-Z, 2-7).
• issuer, the service name, shown in the authenticator app. Redundant with the label but improves UX on apps that don't parse the label.
• algorithm, SHA1 (default), SHA256, or SHA512. Every authenticator supports SHA1; fewer support SHA256/SHA512.
• digits, 6 (default) or 8. Most consumer apps expect 6.
• period, TOTP only. 30 (default) or 60 seconds. HOTP has a counter parameter instead.

Kanoniske testvektorer

Live Base32-hemmelighetvalidator

Autentiseringsapper avviser hemmeligheter som inneholder noe utenfor Base32-alfabetet (A-Z, 2-7). Nedenfor er den samme validatoren Abundera kjører innebygd i TOTP-generatoren, kjører i nettleseren din.

Vanlige fallgruver

• Base32 is not Base64. Base64 uses A-Z, a-z, 0-9, +, /, any of those lowercase letters or digits 0, 1, 8, 9 in your secret means you were handed a Base64 string and it'll be rejected by every authenticator.
• Secret length. RFC 4226 §4 recommends at least 128 bits (26 Base32 chars) for HOTP and 160 bits (32 chars) for TOTP. Secrets under 80 bits (16 chars) are technically legal but flagged weak.
• Algorithm support varies. Google Authenticator ignores the algorithm parameter and always uses SHA1. For SHA256/SHA512 to actually take effect, your users must be on 1Password, Authy, Bitwarden, or Microsoft Authenticator.
• Digits support varies. Most authenticators ignore digits=8 and silently truncate to 6. If 8-digit OTPs matter (banking, some government apps), test your target authenticator before rolling out.
• URL-encode the label. Special characters in issuer or account (:, @, space) must be percent-encoded in the label, or older authenticators drop the label entirely. Abundera handles this automatically.
• Never reuse secrets. Every account gets a fresh cryptographically-random secret. Reusing a secret across services means a compromise at one breaks all of them.
• Storage matters more than the QR. The QR is a one-time bootstrap. The authenticator app stores the secret after the first scan. If that secret is later exported in plain text (some authenticators do this), one disk leak = every 2FA compromised.

Autentiseringskompatibilitet

Se også

• /totp-2fa-qr-code/, the TOTP generator with Base32 validator inline.
• /hotp-qr-code/, HOTP counter-based variant.
• /standards/, back to the standards index.

Spesifikasjonsreferanser verifisert 2026-04-18. RFC 6238 (2011), RFC 4226 (2005), Google Key URI Format.