Configure SAML 2.0 single sign-on between Microsoft Entra ID (Azure AD) and Atlan so your users sign in to Atlan with their existing Microsoft credentials. Exchange service provider and identity provider metadata, assign users in Entra, and optionally sync Azure AD groups to Atlan.
Configure SAML 2.0 single sign-on between Google Workspace and Atlan so your users sign in to Atlan with their Google credentials. Exchange service provider and identity provider metadata, assign users in Google Admin Center, and optionally sync Google groups to Atlan.
Configure SAML 2.0 single sign-on between JumpCloud and Atlan so your users sign in to Atlan with their JumpCloud credentials. Exchange service provider and identity provider metadata, assign user groups in JumpCloud, and optionally sync JumpCloud groups to Atlan.
Configure SAML 2.0 single sign-on between Okta and Atlan so your users sign in to Atlan with their Okta credentials. Exchange service provider and identity provider metadata, assign users in Okta, and optionally sync Okta groups to Atlan.
Configure SAML 2.0 single sign-on between OneLogin and Atlan so your users sign in to Atlan with their OneLogin credentials. Exchange service provider and identity provider metadata, assign users in OneLogin, and optionally sync OneLogin groups to Atlan.
Configure SAML 2.0 single sign-on between any SAML-compatible identity provider and Atlan so your users sign in with their existing IdP credentials. Exchange service provider and identity provider metadata, then optionally sync IdP groups to Atlan.
Set up authentication for Atlan: configure SSO with Okta, Azure AD, Google, JumpCloud, OneLogin, SAML 2.0, or PingFederate; automate the user lifecycle with SCIM; and set sign-in rules for new users.
Set up single sign-on (SSO) so your team signs in to Atlan with their existing identity provider credentials. Configure SAML 2.0 with Okta, Azure AD, Google, JumpCloud, OneLogin, PingFederate, or any custom SAML provider.
Configure SAML 2.0 single sign-on between PingFederate and Atlan so your users sign in to Atlan with their PingFederate credentials. Copy Atlan's service provider metadata into PingFederate, configure both ACS endpoints, and import PingFederate's IdP metadata back into Atlan.
Map identity provider groups to Atlan groups so each user's group membership updates automatically on every sign-in, without manual edits in Atlan.
Sync Atlan roles from OIDC or SAML claims so each user's role updates automatically on every sign-in, without manual edits.
Fix the most common IdP group sync problems in Atlan, including groups not syncing, wrong members, and stale memberships after an IdP change.