> 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.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-adfs-as-the-identity-provider-using-saml-2.0/define-the-claim-issuance-policy.md).

# Define the Claim Issuance Policy

You need to define the claim issuance policy. Before you start you need to create the Relying Party Trusts as described in [Create Relying Party Trust in ADFS](/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-adfs-as-the-identity-provider-using-saml-2.0/create-relying-party-trust-in-adfs.md).

1. From the right menu pane of the Relying Party Trusts, click **Edit Claim Issuance Policy**

   ![adfs-edit-claim.png](/files/fz7pw8ik5UXIOGr6djZ8)
2. Click **Add Rule**.
3. In the Add Transform Claim Rule Wizard, select **Transform an Incoming Claim** from the drop down list.

   ![adfs-add-transform-claim.png](/files/zqR7Th8unYFWoHcTGdep)
4. Click **Next**.
5. In the Configure Claim Rule page, type the Claim rule name **`WindowsAccountName`** which will pass the user login name in AD and select the Windows account name for the Incoming and Outgoing claim type.
6. Click **Finish**.
7. Add another claim rule which will pass the AD user account attributes to Cortex XSOAR. This step is required to map the user group membership, full name, email, phone and other LDAP attributes.
   1. From the right menu pane of the Relying Party Trusts, click **Edit Claim Issuance Policy**
   2. Click **Add Rule**.
   3. In the Add Transform Claim Rule Wizard, select **Send LDAP Attributes as Claims** from the drop down list.
   4. Click **Next**.
   5. In the Configure Claim Rule page, type a claim rule name, select Active Directory from the Attribute store drop down list and map the required fields. Note that the user group attribute is mandatory if you wish to map the user group to the Cortex XSOAR user role.

      ![adfs-edit-rule.png](/files/szlf75Es2ImalmrSDmsX)
   6. Click **Finish** and then click **OK** to create the claim rules.
8. Open PowerShell and make sure the IDP Sign-on page is enabled

   ![adfs-powershell.png](/files/twYq3DyxUXNY2rgrC3gH)

   If one of these setting are set to false, enable it by typing **`Set-AdfsProperties -<Property Name RelayState or EnableIdp> $True`**
9. Verify that the ADFS IDP Sign-on page is working by browsing to the ADFS service portal URL, in our example: <https://demistodev.local/adfs/ls/idpinitiatedsignon.aspx>
10. Continue with [Configure the SAML 2.0 Integration for ADFS](/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-adfs-as-the-identity-provider-using-saml-2.0/configure-the-saml-2.0-integration-for-adfs.md).


---

# 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.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0/set-up-adfs-as-the-identity-provider-using-saml-2.0/define-the-claim-issuance-policy.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.