Overview
Two-Factor Authentication (2FA) adds an additional security layer beyond username and password. Users must provide a second factor - typically a time-based one-time password (TOTP) from an authenticator app - to access Forest.Recommended for All Users: 2FA significantly reduces the risk of unauthorized access, even if passwords are compromised.
Supported 2FA methods
Authenticator apps (recommended)
Time-based One-Time Password (TOTP) apps generate 6-digit codes that change every 30 seconds:Google Authenticator
Free app for iOS and Android
Microsoft Authenticator
Supports backup and cloud sync
Authy
Multi-device support with encrypted backups
1Password
Password manager with built-in TOTP
Bitwarden
Open-source with TOTP support
LastPass Authenticator
One-tap push notifications
Backup codes
Recovery codes to use if you lose access to your authenticator app:- Generated during 2FA setup
- One-time use only
- Store securely (password manager or printed copy)
- Can regenerate if needed
Enabling 2FA (for users)
Setup process
Scan QR Code
- Open your authenticator app
- Tap “Add account” or ”+” button
- Scan the QR code displayed in Forest
Save Backup Codes
- Download or copy your backup codes
- Store them securely (password manager recommended)
- Check the box to confirm you’ve saved them
Manual setup key
If you can’t scan the QR code, use the manual setup key:Using 2FA to log in
Login flow
Using backup codes
If you don’t have access to your authenticator app:Trusted devices
Mark devices as trusted to skip 2FA for 30 days:- Use Case: Your primary work computer
- Security: A secure cookie identifies the device
- Removal: Go to Account Settings > Security > Trusted Devices to revoke
Enforcing 2FA (for admins)
Administrators can require 2FA for all users or specific roles.Project-wide enforcement
Require 2FA for everyone:Set Grace Period
Choose how long users have to enable 2FA:
- 24 hours (urgent)
- 7 days (recommended)
- 30 days (gradual rollout)
Role-based enforcement
Require 2FA only for specific roles:- Go to Project Settings > Roles
- Edit each role
- Check Require 2FA for this role
Exceptions
Allow specific users to bypass 2FA requirement:- Use Case: Emergency access accounts, service accounts, external contractors
- Configuration: Edit user profile > Security > Exempt from 2FA requirement
Best Practice: Minimize exceptions. If a user truly needs access, they should enable 2FA.
Managing 2FA
Regenerating backup codes
If you’ve used all your backup codes or lost them:Resetting your own 2FA
If you need to switch authenticator apps or devices:Admin: resetting user’s 2FA
If a user loses access to their authenticator and backup codes:Verify User Identity
Confirm the user’s identity (don’t rely solely on email, which could be compromised)
2FA + SSO
How they work together
2FA and SSO can be used simultaneously for defense in depth:- IdP-Based 2FA (Recommended)
- Forest 2FA + SSO
- SSO Only (No Forest 2FA)
MFA enforced at identity provider
- User authenticates with IdP (e.g., Okta, Azure AD)
- IdP requires MFA (push notification, TOTP, etc.)
- Forest trusts the IdP’s authentication
- Centralized MFA management
- One MFA prompt for all applications
- Better user experience
Recommended configuration
For SSO Users
Enforce MFA at the IdP levelDisable Forest 2FA for SSO users to avoid double-prompting
For Password Users
Require Forest 2FAThese users don’t benefit from IdP security
Troubleshooting
Code not working
Time Sync Issues
Time Sync Issues
Problem: Authenticator app time is out of syncSymptoms: Code is always rejected, even when entered correctlySolution:
- Check your phone’s time settings
- Enable automatic time/date
- Try the next code (they change every 30 seconds)
- Go to Settings > Time correction for codes > Sync now
Wrong Code Entered
Wrong Code Entered
Problem: Entering an old or incorrect codeSolution:
- Wait for the code to refresh in your app
- Ensure you’re using the correct account (if you have multiple)
- Check for typos (0 vs O, 1 vs l)
Authenticator App Deleted
Authenticator App Deleted
Problem: Removed app or factory reset phone without backing upSolution:
- Use a backup code if you have one
- Contact your admin for 2FA reset
- Admin must verify your identity before resetting
Can’t scan QR code
Solutions:- Use Manual Entry: Copy the setup key and enter it manually in your authenticator app
- Try Different Device: Use a tablet or another phone to scan
- Check Camera Permissions: Ensure authenticator app has camera access
- Screenshot: Take a screenshot (secure it afterwards) and scan from photos
Lost backup codes
If you still have authenticator access:- Log in with your authenticator code
- Regenerate new backup codes
- Save them securely
- Contact your administrator
- Admin will verify your identity
- Admin can reset your 2FA
- Set up 2FA again immediately
Can’t log in after 2FA enforcement
Problem: 2FA was enforced but user hasn’t set it up Solution:- Users receive grace period to enable 2FA
- During grace period, they’re prompted to set up 2FA
- After grace period, they must set up 2FA before accessing
- Admin can temporarily exempt user from 2FA requirement
- User can then log in and set up 2FA properly