Understanding TOTP (2FA) in Blinkr
Time-based One-Time Passwords (TOTP) are a crucial layer of security for modern web apps. Blinkr automates this process so you can stay secure without the friction of manual code entry.
How Blinkr Handles 2FA
Normally, 2FA requires you to open an app like Google Authenticator and type a 6-digit code. In Blinkr, this process is handled entirely within our secure environment:
Encrypted Storage
Your admin stores the secret key (base32) for the 2FA account in the Blinkr vault, encrypted with your org's key.
Server-side Generation
When you log in, our server generates the 6-digit code in real-time. The secret key is never sent to your browser.
Automated Injection
The extension receives the current code and injects it directly into the 2FA field on the website.
Setting up TOTP (For Admins)
Admins can add TOTP to any credential set in the dashboard. We support three ways to add a secret:
- Manual Secret: Enter the base32 secret key provided by the site.
- OTP URI: Paste the full
otpauth://totp/...link. - QR Code: Upload an image of the 2FA QR code for automatic parsing.
Why this is more secure
By using Blinkr for TOTP, the organization maintains ownership of the second factor. If a team member leaves, you don't need to reset 2FA on the target account because the user never had the secret on their personal phone.