What is an authenticator app, and how does it work?
Key takeaways
- Most authenticator apps use time-based one-time passwords, which combine a secret shared during QR code setup with the current time and are calculated locally.
- Save the recovery codes the service provides and register a backup method before signing out, so you can regain access without your phone.
- App codes avoid SMS interception and SIM-swap attacks, but a fake website can still capture and relay them, so check where you sign in.
- Deny any approval request you did not start, and never read a verification code aloud to someone claiming to be support.
An authenticator app helps protect your online accounts by generating temporary sign-in codes or asking you to approve a login. Used alongside a password, it adds another check before someone can access your account. These answers explain how authentication works, how to set it up, and how to avoid losing access when something goes wrong. (cisa.gov)
What does an authenticator app actually do?
An authenticator app provides evidence that you control a registered authentication device or credential. In a common setup, you enter your account password, then type a short code displayed in the app. Someone who steals only your password would still need the additional authentication factor to complete that sign-in. (pages.nist.gov)
Some apps also receive approval requests instead of requiring a typed code. Others support passwordless sign-in for compatible accounts. These are different authentication methods within the same broad app category, so the experience depends on both the app and the service you are accessing. (support.microsoft.com)
How does an authenticator app generate its codes?
Many authenticator apps use time-based one-time passwords, or TOTP. During setup, the service shares a secret key with your app, usually through a QR code. The app combines that secret with the current time to calculate a temporary code; the service performs a matching calculation to check your entry. (cheatsheetseries.owasp.org)
The standard recommends a default interval of 30 seconds, although implementations can differ. The changing numbers are not messages being sent to your phone: they are calculated locally. That is why an accurate device clock matters and why a saved code cannot serve as a permanent login credential. (datatracker.ietf.org)
What is the difference between two-factor authentication and multi-factor authentication?
Two-factor authentication, or 2FA, requires two distinct types of evidence. Multi-factor authentication, or MFA, means two or more. The main categories are:
- Something you know: a password or PIN.
- Something you have: an authenticator credential or security key.
- Something you are: a biometric characteristic, such as a fingerprint. (cheatsheetseries.owasp.org)
A password followed by an authenticator code is a common two-factor combination. A password followed by another password is not: both belong to the same category. The important distinction is the independence of the factors, not simply how many screens or steps appear during login. (cheatsheetseries.owasp.org)
Is an authenticator app the same as a password manager app?
No. A password manager app primarily stores and fills passwords, while an authenticator generates verification codes or handles supported authentication requests. Some password managers can also generate authenticator codes, so the categories can overlap. Check the actual features rather than assuming every security app performs both jobs. (cisa.gov)
Keeping passwords and verification codes together is convenient, but it also concentrates access in one place. Separate storage can reduce that concentration, provided each tool is protected and recoverable. Whichever arrangement you use, secure the password vault and avoid making its only recovery route depend on credentials stored inside that same vault. (cheatsheetseries.owasp.org)
How do I set up an authenticator app?
Start in the security settings of the account you want to protect. Installing an app alone does not enable account protection; you must connect it to each supported service. The usual process is:
- Install the app from the provider’s official app-store listing.
- Open account security settings and find two-factor authentication, multi-factor authentication, or two-step verification.
- Choose an authenticator app as an available method.
- Scan the displayed QR code using the app, or enter the setup key manually if offered.
- Enter a generated code on the service’s setup page to confirm the connection. (support.microsoft.com)
Before signing out, save any recovery codes the service provides. Also register an additional recovery method where available. Setup is not complete from a practical standpoint until you know how to regain access without your phone. (support.google.com)
What should I do with the setup QR code?
Treat the setup QR code and manual secret key as sensitive credentials. They contain the information needed to configure code generation. Someone who obtains that secret may be able to generate the same verification codes, so do not post it in a support forum or send it in an ordinary chat. (cheatsheetseries.owasp.org)
If you deliberately retain a backup, protect it against unauthorized access. Avoid leaving an unprotected screenshot in a shared photo library. Recovery codes and setup keys serve different purposes: recovery codes provide a service-defined fallback, while the setup secret can reproduce the authenticator credential. (cheatsheetseries.owasp.org)
Do authenticator apps work without internet or cell service?
Time-based code generation generally works offline once the account is configured. Your app needs the stored secret and an accurate clock, not a text message or live mobile connection. This can be useful when traveling, using airplane mode, or signing in somewhere with poor reception. (datatracker.ietf.org)
Push approvals are different: the phone needs connectivity to receive and complete the request. Account synchronization and backup restoration also depend on connectivity. Separately, the device accessing an online service still needs a connection to submit your login, even if your phone generates the verification code offline. (support.microsoft.com)
Can one authenticator app protect several accounts?
Yes. An authenticator can hold entries for multiple supported services, including personal, work, and school accounts. You do not necessarily need a separate app for every website, but each account must be enrolled individually. Adding your email account does not automatically protect your shopping or social accounts. (support.microsoft.com)
Compatibility still matters. Many services accept standard TOTP apps, while some require a particular product or organization-managed method. Label entries clearly, especially when you have personal and work accounts with the same provider, so you select the correct code at sign-in. (cheatsheetseries.owasp.org)
Are authenticator apps safer than text-message codes?
App-generated codes avoid several weaknesses associated with SMS authentication, including interception through telecommunications systems and attacks that transfer your phone number to another SIM. They do not depend on receiving a message at your number. CISA places app-based OTP authentication above SMS in its guidance on authentication methods. (cisa.gov)
However, authenticator codes are still vulnerable to phishing. A fraudulent website can ask for your password and current code, then relay both to the real service. App-based authentication improves protection, but it does not make every page requesting a code trustworthy or eliminate the need to check where you are signing in. (nist.gov)
Can an authenticator app replace my password?
Sometimes, but generating a code does not automatically make an account passwordless. In a conventional password-plus-code setup, you still enter both. Supported services may instead offer passwordless approval through an authenticator app, with device verification helping authorize the sign-in. (support.microsoft.com)
Passkeys are another option, using cryptographic authentication rather than a manually entered shared code. FIDO-based passkeys and security keys can provide phishing resistance that ordinary authenticator codes lack. Use the options supported by your service, and do not delete an existing login method until the replacement and recovery arrangements work. (cisa.gov)
Why is my authenticator app not working?
An authenticator app not working can mean an expired code, the wrong account entry, an inaccurate clock, or a notification problem. Identify which type of authentication is failing before changing settings. For rejected time-based codes:
- Wait for a fresh code and enter it promptly.
- Check that the entry matches the service and username.
- Set the phone’s date and time to automatic.
- Check whether you are using an obsolete entry after changing authentication settings. (support.google.com)
For missing push requests, check connectivity, notification permissions, and battery restrictions. Update the app and restart the device if necessary. Avoid deleting entries or reinstalling immediately: first verify that you have a usable backup or another sign-in method. (support.microsoft.com)
What should I do if I receive an approval request I did not initiate?
Deny an unexpected request. Do not approve it to stop repeated notifications, and never read a verification code to someone claiming to be support. Attackers may pressure you to authorize access or describe the request as a security check. (support.microsoft.com)
Open the service directly through its known app or website, rather than following a message link. Review available sign-in activity and secure the account if anything looks unfamiliar. For a work or school account, report unexpected requests to your IT team so they can investigate rather than treating repeated prompts as a harmless nuisance. (support.google.com)
How do I move my authenticator to a new phone?
Use the app’s documented transfer or restoration process before erasing your old phone. Google Authenticator supports account synchronization and manual transfer. Other products have their own backup requirements, and restoring an app does not necessarily restore every account to a fully usable state. (support.google.com)
Follow this order:
- Confirm your backup or transfer method.
- Restore or transfer the credentials.
- Test a sign-in for each important account.
- Complete any required account re-registration.
- Remove the old device’s access where appropriate, then erase it before disposal. (support.microsoft.com)
Keep the old phone available until testing is complete. Seeing an account name on the new device is not sufficient proof that authentication works. (support.microsoft.com)
What happens if my phone is lost, stolen, or broken?
Use a previously registered alternative, such as a recovery code, security key, or another supported verification method. If none is available, follow the service’s official recovery process. For organization-managed accounts, your administrator may need to reset your authentication registration; the authenticator provider cannot necessarily recover access to an unrelated service. (support.google.com)
A stolen phone also requires a security response. Use available device-locking or remote-erasure tools, review account access, and replace exposed authenticator registrations where needed. Keep recovery information somewhere you can access without that phone; otherwise, a backup may exist but be unusable when you need it. (support.google.com)
How do I remove a password or account from Google Authenticator?
Google Authenticator entries are verification credentials, not ordinary saved passwords. If you mean deleting a code entry, first change the authentication method in the relevant service’s security settings. Deleting the app entry does not tell that service to stop requiring its code. (support.google.com)
On Android, swipe right on the entry to reveal deletion, then confirm. Synced deletion also removes the entry from other synced devices. If you mean removing the app’s PIN or biometric prompt, that is its Privacy Screen feature, not your account password. Keeping access protection enabled helps protect exposed codes. (support.google.com)
Does an authenticator app protect everything on my phone?
No. An authenticator is a specialized mobile security app for account authentication, not a complete defense against malware, unsafe downloads, or compromised devices. A phone infection or unauthorized device access can still threaten authentication credentials. Protecting the device remains part of protecting the accounts connected to it. (cisa.gov)
Use a screen lock, enable the authenticator’s access protection where available, and keep the device and app updated. Maintain an independent recovery route as well. The goal is not simply to add another login step, but to make unauthorized access harder without leaving yourself locked out. (support.microsoft.com)
Related guides
Sources
- cisa.gov: Fact sheet implementing phishing resistant mfa 508c
- NIST Special Publication 800-63B
- How to add your accounts to Microsoft Authenticator | Microsoft Support
- Multifactor Authentication - OWASP Cheat Sheet Series
- RFC 6238 - TOTP: Time-Based One-Time Password Algorithm
- cisa.gov: Guidance mobile communications best practices
- Download Microsoft Authenticator | Microsoft Support
- Fix common issues with 2-Step Verification - Google Account Help
- Authentication did not complete | Microsoft Support
- Phishing Resistance – Protecting the Keys to Your Kingdom | NIST
- Get verification codes with Google Authenticator - Android phone & tablet - Google Account Help
- Troubleshoot problems with Microsoft Authenticator | Microsoft Support
- Microsoft Authenticator FAQs | Microsoft Support
- Turn on 2-Step Verification - Computer - Google Account Help
- Back up one-time password codes in Microsoft Authenticator | Microsoft Support
- Get verification codes with Google Authenticator - Android phone & tablet - Google Account Help
- cisa.gov: Csso scuba guidance document hybrid identity solutions architecture 2023.03.14 final