An identity provider (IdP) authenticates users and supplies identity information to relying services. In Atlas, it centralizes organizational credentials for federated authentication, allowing users to authenticate across multiple online services. section 20.2
An identity provider participates in Atlas security by:
- Authenticating Atlas UI users through federated identity management while the organization retains control of credentials. section 20.2
- Supporting external providers such as Okta, GitHub, Google, Ping Identity, and Microsoft Entra ID. section 20.2
- Working alongside MFA, RBAC, and database-specific authentication methods rather than replacing database access controls. section 20.8
- Remaining a customer-managed responsibility within Atlas’s shared responsibility model, including federation, LDAP, and MFA configuration. section 20.1
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, including SCRAM, X.509, LDAP, OIDC, AWS IAM, and Vault integration. section 20.2
Federated login in Atlas
An organization configures Atlas Federated Authentication with an external identity provider. Users authenticate through the organization’s credential system, while Atlas applies assigned roles to control access to cloud resources and deployments. section 20.8
