Note
This page covers MongoDB Atlas for Government user accounts. AtlasGov users are separate from database users. Database users can access MongoDB databases, while AtlasGov users can access the AtlasGov application itself.
One-Time Password and MFA Migration Flow
As part of the transition of AtlasGov to an improved authentication environment, password users must go through a one-time self-service migration when they log in on or after March 18, 2026.
Important
Migration deadline
To ensure a smooth migration to the new authentication environment:
You must log in to AtlasGov and complete the one-time MFA migration flow by June 30, 2026.
Users who do not log in by this date might require a full account recovery before they can access AtlasGov again.
If you are an organization owner, we recommend that you notify impacted users and ensure they log in before the migration deadline.
To complete the one-time password and MFA migration flow:
Complete a one-time MFA challenge with your existing factors.
AtlasGov prompts you to verify your identity using your existing MFA factors (for example, a security key, biometric factor, or TOTP code).
This page will look slightly different from your usual MFA screen, but it uses your current factors for verification.
Enroll MFA in the new environment.
After you successfully verify your account with your existing factor, AtlasGov prompts you to configure at least one more authentication factor in the new environment. Depending on your organization's policies, you might register one or more of the following authentication factors:
Security key or biometric factor (WebAuthn).
Time-based one-time password (TOTP) authenticator app.
Add additional factors your organization allows.
Troubleshoot Password and MFA Migration
Use the following guidance if you or another user encounters issues during the one-time password and MFA migration.
I can't verify my existing security key or biometric factor
If you have another MFA factor configured (for example, a TOTP authenticator app), approve the challenge using that factor.
If you do not have any alternate factor configured, do one of the following steps:
Contact your organization owner so they can open a case with MongoDB Support through the AtlasGov Support Portal.
If you are an organization owner, open a Support case and include affected usernames and organization details.
MongoDB Support can help you recover access and re-enroll MFA factors as needed. To learn more, see Support.
I forgot my password and still can't log in after resetting it
If you reset your password, but still can't complete the migration or log in:
If needed, request support.
If you continue to experience issues (for example, loops between password reset and MFA prompts, do one of the following steps:
Contact your organization owner.
Open a case with MongoDB Support from the AtlasGov Support Portal. To learn more, see Support.
I lost access to all of my MFA factors
If you no longer have access to any of your configured MFA factors (for example, you lost your security key or no longer have access to the authenticator app):
Contact your organization owner or MongoDB Support.
To learn more, see Support.
I did not complete the migration before the deadline
If you do not log in to AtlasGov and complete the migration flow before June 30, 2026, your account might require a full account recovery:
Organization owners should open a case with MongoDB Support and provide a list of impacted users.
MongoDB Support will guide you through the recovery process for both password and federated accounts that did not complete migration before the deadline.
To learn more, see Support.