> 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/configure-the-saml-2.0-integration-for-okta/saml-2.0-okta-parameters.md). # SAML 2.0 Okta Parameters The following table describes the SAML 2.0 parameters for Okta when adding a new instance in Cortex XSOAR. | Attribute | Description | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Name | A name for the integration instance. | | Service Provider Entity ID | The URL of your Cortex XSOAR server (also known as an ACS URL). In the format: | | IdP metadata URL |

URL of your organization’s IdP metadata file. You can find this in the Sign On tab in Otka or when defining an Okta application, as described in Define the Okta Application to authenticate Cortex XSOAR.

okta-setup.png

| | IdP metadata file | Your organization’s IdP metadata file. You either need to add the IdP metadata URL or the file. | | IdP SSO URL | The URL of the IdP application that corresponds to Cortex XSOAR. You can copy and paste the IdP SSO URL in Okta, when clicking **View Setup Instructions**. | | Attribute to get username | Attribute in your IdP for the user name. | | Attribute to get email | Attribute in your IdP for the user's email address. | | Attribute to get first name | Attribute in your IdP for the user's first name. | | Attribute to get last name | Attribute in your IdP for the user's last name. | | Attribute to get phone | Attribute in your IdP for the user's phone number. | | Attribute to get groups | Attribute in your IdP for the groups of which the user is a member. | | Groups delimiter | Groups list separator. | | Default role | Role to assign to the user when they are not a member of any group. | | RelayState | Only used by certain IdPs. If your IdP uses relay state, you need to supply the relay state. | | Sign request and verify response signature | Method for the IdP to verify the user sign-in request using the IdP vendor certificate. | | Identity Provider public certificate | Public certificate for your IdP. | | Private key | Service Provider Private key (pem format). | | Do not map SAML groups to Cortex XSOAR roles | SAML groups will not be mapped to Cortex XSOAR roles. | --- # 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/configure-the-saml-2.0-integration-for-okta/saml-2.0-okta-parameters.md?ask=&goal= ``` `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.