> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xpanse/users-and-roles/user-authentication/use-multiple-saml-2.0-providers.md).

# Use Multiple SAML 2.0 Providers

Configure multiple SAML SSO providers and route users to the correct identity provider by email domain.

In Cortex Xpanse, you can use multiple SAML SSO providers.

To view providers, go to **Settings** → **Configurations** → **Access Management** → **Single Sign-On**. To add an additional provider, **Add SSO Connection**.

When using two or more SSO providers:

* The first provider in the list is used as the default SSO provider. The **Domain** parameter is predefined for the first SSO.
* If you add additional SSO providers, you must provide the email **Domain** in the SSO Integration settings for all providers except the first. Cortex Xpanse uses this domain to determine which identity provider the user should be sent to for authentication. At the Cortex Xpanse login page, if you have enabled more than one SSO provider, an optional email field displays above the **Sign-In with SSO** button. If the user does not enter an email address in this field or if the email address does not match an existing domain, the user is automatically directed to the default IdP provider (the first in the list of SSO providers). If the user enters an email address and it matches a domain listed in the email **Domain** field in the SSO Integration settings for one of your IdPs, **Sign-In with SSO** sends the user to the IdP associated with that email domain.
* When mapping IdP user groups to Cortex Xpanse user groups, you must include the group attribute for each IdP you want to use. For example, if you are using Microsoft Azure and Okta, your Cortex Xpanse user group **SAML Group Mapping** field must include the IdP groups for each provider. Each group name is separated by a comma.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xpanse/users-and-roles/user-authentication/use-multiple-saml-2.0-providers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.