> 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.14/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-okta-as-the-identity-provider-using-saml-2.0/define-the-okta-application-to-authenticate-cortex-xsoar/saml-settings-for-the-okta-application.md).

# SAML Settings for the Okta Application

The following tables describes the SAML settings for Okta.

**General Parameters**

| Parameter                       | Value                                                                                    |
| ------------------------------- | ---------------------------------------------------------------------------------------- |
| Single sign on URL              | https\://`<cortexxsoarURL>`/saml                                                         |
| Audience URI (SP Entity ID)     | https\://`<cortexxsoarURL>`/saml/metadata                                                |
| Default RelayState              | Keep this field empty.                                                                   |
| Name ID format                  | EmailAddress. The Cortex XSOAR username is the user's email address, as defined in Okta. |
| Application username            | Okta username.                                                                           |
| Update application user name on | Create and update                                                                        |

![okta-gen-sett.png](/files/sFd32XplocYeI0R0iW2L)

**Attribute Statement Parameters**

| Name      | Name Format | Value             |
| --------- | ----------- | ----------------- |
| FirstName | Unspecified | user.firstName    |
| LastName  | Unspecified | user.lastName     |
| Email     | Unspecified | user.email        |
| login     | Unspecified | user.login        |
| Phone     | Unspecified | user.primaryPhone |

![okta-att.png](/files/gvZDPkXte2IFZHEUa1cT)

**Group Attribute Statement parameters**

| Name     | Name format | Filter | Name of group                       |
| -------- | ----------- | ------ | ----------------------------------- |
| memberOf | Unspecified | Equals | Name of the group you have created. |

The Group Attribute Statement parameters define which groups to associate with Cortex XSOAR and which groups are to be mapped to Cortex XSOAR roles. In this example, add a group called Everyone.

![okta-group.png](/files/O9lQDkD8tjhrymFCDW2o)

{% hint style="info" %}

### Note

If you are using **memberOf** as a group attribute statement, ensure not to use the **memberOf** as an attribute statement. You cannot have both single user and group user attributes.
{% endhint %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-okta-as-the-identity-provider-using-saml-2.0/define-the-okta-application-to-authenticate-cortex-xsoar/saml-settings-for-the-okta-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.