Skip to main content
SAML single sign-on lets members sign in to Arize AX through your identity provider, with no separate Arize password. Role mappings assign Arize roles from identity provider attributes at each sign-in, so access follows your company directory and you do not set roles by hand in Arize.
SAML is available on AX Enterprise accounts.
Create SAML configuration panel with email domains, metadata URL, and sign-in settings

Connect your identity provider

SAML is configured under Settings → Account Settings → SAML.
  1. Add the email domains for this configuration, such as company.com or *.company.com.
  2. Enter the identity provider’s metadata URL or paste its XML. The URL must use HTTPS with no port number.
  3. Choose the sign-in settings and continue to role mappings.
Arize Support verifies each new domain. SAML sign-in does not work for a domain until it is verified. Each domain shows Verified or Not verified when you edit the configuration.

Sign-in settings

  • Allow only SAML logins turns off password login for these domains. Arize Support cannot sign in to help. Make sure at least one administrator can sign in through the identity provider before turning this on. While it is on, POST /v2/users invitations return 400.
  • Sync permissions on each login resets each user’s roles to the role mappings at every sign-in. Roles changed by hand in Arize are overwritten.
  • Allow login to a default organization and space lets users with no matching role mapping sign in. They join the default organization and space. Without this setting, those users cannot sign in.
Create role mappings before turning on Sync permissions on each login. Without mappings, every user is reset to the default organization and space, or login fails when no default is allowed.

Map roles

A role mapping assigns Arize roles to users whose SAML attributes match, such as department equal to engineering. A mapping matches on one or more attribute names and values. All pairs must match the assertion. The mapping sets:
  • Account Admin, which grants Account Admin access. A wrong admin mapping can lock people out, including you. Check it before signing out.
  • Account role: Account Member or Account Member - UI Only.
  • Organization and Organization role.
  • Space and Space role, including custom roles. More spaces can be added.
  • Project assignments inside a space assignment: Viewer, Editor, Admin, or a custom role on a restricted project in that space.
A user who matches more than one mapping gets the highest account, organization, and space role across them. Only one custom role can apply per space, so for custom roles the first matching mapping wins. A per-user developer access override is kept when a login leaves the account role unchanged.

Caching

Domain, metadata, sign-in setting, and role mapping changes take effect within 5 minutes. Role mappings are applied at login, so a signed-in user picks up a mapping change at their next login, which happens within 24 hours or immediately after they log out.