> 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/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0.md).

# Authenticate Users with SAML 2.0

Authenticate Cortex XSOAR 6.15 users with SAML 2.0 identity providers, including Okta, Microsoft Entra ID, ADFS, and Duo.

SAML exchanges authentication and authorization data between security domains. SAML 2.0 is an XML-based protocol that uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority (Identity Provider) and a SAML consumer (Service Provider).

SAML 2.0 enables web-based authentication and authorization scenarios including cross-domain single sign-on (SSO), which helps reduce the administrative overhead of distributing multiple authentication tokens to the user. For more information about SAML 2.0, see [SAML 2.0 Wikipedia](https://en.wikipedia.org/wiki/SAML_2.0).

You can authenticate your Cortex XSOAR users using SAML 2.0 authentication with your identity provider, such as Okta. You need to define Cortex XSOAR authentication in your Identity Provider’s account, then create a SAML 2.0 instance in Cortex XSOAR:

* [Set up Okta as the Identity Provider Using SAML 2.0](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-okta-as-the-identity-provider-using-saml-2.0.md)
* [Set Up Microsoft Entra ID as the Identity Provider Using SAML 2.0](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-microsoft-entra-id-as-the-identity-provider-using-saml-2.0.md)
* [Set up ADFS as the Identity Provider Using SAML 2.0](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-adfs-as-the-identity-provider-using-saml-2.0.md)

When configuring the SAML 2.0 integration instance, in the third party application, if the SAML configuration contains the LDAP URL for name, email, phone, SAML populates the user's email field in Cortex XSOAR.

If the third party SAML configuration for name, email, phone is left blank, the administrator can modify the user properties and manually enter the information. To set this up, you need to add the following server configuration (Settings → ABOUT → Troubleshooting → **Add Server Configuration**):

| Key                         | Value      |
| --------------------------- | ---------- |
| **`saml.stick.userfields`** | **`true`** |

This server configuration does not change, no matter how many times you log into or out of Cortex XSOAR. The only time the configuration is overwritten is when the SAML configuration contains the LDAP URL for email or when it is changed manually in the third-party application.


---

# 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 dynamically 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/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0.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 `build a script that syncs our docs to a CMS` 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.