Federated identity integration lets an external identity provider authenticate users across multiple relying services. In MongoDB Atlas, the organization manages user credentials through its identity provider, while Atlas uses that identity for Atlas UI access. section 20.2 section 20.8
Apply the integration with these operational boundaries:
- Configure federation, identity providers, and MFA as customer-controlled security settings. section 20.1
- Use Atlas roles and permissions separately to control which users or applications can access or modify data. section 20.2 section 20.8
- Treat federated Atlas UI login as distinct from database-cluster authentication, which can use SCRAM, X.509, LDAP, OIDC, or AWS IAM. section 20.2 section 20.8
Atlas UI sign-in
An organization connects an external provider such as Okta, GitHub, Google, Ping Identity, or Microsoft Entra ID. A user authenticates with that provider, and Atlas relies on the provider’s identity information for access; MFA can be enforced for additional protection. section 20.2 section 20.8
Table 20.2 Authentication features in Atlas
| Feature |
Description |
| Atlas Federated Authentication |
Supports login through external identity providers such as Okta, GitHub, Google, Ping Identity, and Microsoft Entra ID |
| Ensures secure database access with Salted Challenge Response Authentication Mechanism (SCRAM), X.509 certificates, LDAP, OpenID Connect (OIDC), and passwordless authentication with AWS IAM Integrates with HashiCorp Vault for dynamic user creation |
Compare Atlas federated authentication with database authentication methods and Vault-backed dynamic credentials. section 20.2
