Skip to main content
The saml_identity_providers client methods are currently in ALPHA. The API may change without notice. A one-time warning is emitted on first use.
Manage SAML single sign-on configurations for your account. A configuration pairs one metadata source (an IdP metadata URL or inline XML) with a set of email domains and login defaults, and carries an ordered list of role mappings that translate SAML assertion attributes into Arize roles. These operations require Enterprise account-admin access.

Key Capabilities

  • List SAML configurations with cursor-based pagination
  • Create a configuration from a metadata URL or inline metadata XML
  • Retrieve, update, and delete a configuration by ID
  • List, add, update, and remove role mappings on a configuration

Request Bodies

Create and update methods take a body argument that is either a typed request model (imported from arize.saml_identity_providers.types) or a plain JSON-compatible mapping with the same fields. Unknown keys in a mapping are rejected before the request is sent.

List SAML Identity Providers

List SAML configurations with cursor-based pagination (up to 100 per page). The returned summaries omit metadata and role mappings — use get for the full configuration.
For details on pagination, field introspection, and data conversion (to dict/JSON/DataFrame), see Response Objects.

Create a SAML Identity Provider

Create a configuration with exactly one metadata source (metadata_url or metadata_xml) and valid login defaults. Domain-verification flags are read-only and cannot be supplied. Non-empty space or project assignments require an organization.
The body may also be a plain mapping with the same fields:

Get a SAML Identity Provider

Retrieve a complete configuration by ID, including file-managed configurations.

Update a SAML Identity Provider

Patch only the fields you supply; omitted fields are left unchanged. Omission, False, None, and empty lists stay distinct. Setting allow_login_with_defaults to False clears all default fields.

Delete a SAML Identity Provider

Remove a disabled configuration by ID. Users and their grants remain. Enforced and file-managed configurations cannot be deleted. There is no response from this call.

Manage Role Mappings

Role mappings translate SAML assertion attributes into Arize roles. Each mapping matches a set of attributes and grants account-admin status, an organization role, and/or space and project roles.

List Role Mappings

List a configuration’s role mappings in configuration order, with cursor-based pagination (up to 100 per page).
For details on pagination, field introspection, and data conversion (to dict/JSON/DataFrame), see Response Objects.

Add a Role Mapping

Add a mapping to a configuration. The server assigns its persistent ID. Non-empty space or project assignments require an organization.

Update a Role Mapping

Patch supplied fields while keeping the mapping ID. Omitted fields remain unchanged. None clears the organization only when the resulting mapping is valid; empty role lists clear assignments.

Remove a Role Mapping

Remove a mapping by ID. Required login and admin mappings are retained. There is no response from this call.