> 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.md).

# User authentication

Authenticate Cortex Xpanse users using SAML 2.0 or the Cortex Gateway.

After you have activated your tenant, you need to configure how users access Cortex Xpanse. You can authenticate users by using one or both of the following options:

* User authentication through the Customer Support Portal (CSP)

  When users log into the Cortex Gateway or the tenant (provided they are assigned a role) they are prompted to sign into the CSP using their username and password or 2FA (if set up). This is the default method of authentication.
* SAML single sign-on in the Cortex Xpanse tenant

  Users can be authenticated using your IdP provider such as Okta, Ping, or Azure AD. You can use any IdP that supports SAML 2.0.

There are several advantages to setting up SSO in the tenant rather than relying on CSP authentication:

* Removes the administrative burden of requiring separate accounts to be configured through the Customer Support Portal.
* Enforces multi-factor authentication (MFA) and any conditional access policies on the user login at the IdP before granting a user access to Cortex Xpanse.
* Maps SAML group memberships to user groups and roles, allowing you manage role based access control.
* Removes access to Cortex Xpanse when a user is removed or disabled in the IdP.

CSP authentication may be useful when you have one CSP account and want the same set of users to have permissions in several tenants.

#### Next step

After setting up authentication, start creating roles, user groups, configure permissions, and manage users in the Cortex Xpanse tenant or the Cortex Gateway.


---

# 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.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.