> 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.12/onboard-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).

# Create Relying Party Trust in ADFS

In ADFS you need to create a Relying Party Trust. The following procedure uses ADFS 3.0 on Windows Server 2016 and shows demistodev.local as the ADFS portal service which will allow a trust connection from the <https://demo.demisto.com> web server.

You must have a valid and trusted server certificate for ADFS to work, not the self-signed certificates that come with Cortex XSOAR. If you do not use a trusted server certificate for ADFS, you will experience TLS connection issues with ADFS and the integration will not work properly.

1. Log in to the ADFS server management console.
2. In the tree in the left panel, right-click **Service** and select **Edit Federation Service Properties**.

   ![adfs-edit-federation-option.png](/files/RlQgkgb2Uu6yQRXBssZS)
3. Click the **General** tab and confirm that the DNS entries and certificates names are correct.

   ![adfs-federation-props.png](/files/6zytrlTfhtKeKbiISNEZ)
4. In the tree in the left panel, right-click **Relying Party Trusts** and select **Add Relying Party Trusts**.

   ![adfs-add-relying-party-trust.png](/files/n4H2q8UCWudKa8U7Ggrg)
5. The Add Relying Party Trust Wizard screen appears. Click **Start**.

   ![adfs-trust-wizard.png](/files/9TfGUTNFK1eseJSqqIVC)
6. In the Select Data Source page, select **Enter data about the relying party manually**.

   ![adfs-wizard-enter-data.png](/files/o1lQVVG6KvGtsHnQwgqn)
7. Click **Next**.
8. In the Specify Display Name page, type a display name for the trust in the Display name field. In this example, the name of the trust is Demisto.

   ![adfs-display-name.png](/files/3o2ZVnKvNfaFzoT2BW8F)
9. Click **Next**.
10. (Optional) In the Configure Certificate page, you can configure the claims encryption.
11. Click **Next**.
12. In the Configure URL page, select **Enable support for the SAML 2.0 Web SSO protocol**, and enter the Cortex XSOAR server URL followed by /SAML.

    ![adfs-configure-url.png](/files/kywYnwkuvNw2hmgpIi76)
13. Click **Next**.
14. In the Configure Identifiers page, add the Relying party trust identifier. The identifier can be a friendly name, the same as the Display name, or the application URL. This identifier is used to redirect the user back to the Cortex XSOAR web server instead of asking the user to manually choose which service should log in to the ADFS IDP portal.

    ![adfs-configure-identifiers.png](/files/JjPVY1Zl6M8fgoURXqOw)
15. Click **Next**.
16. In the Choose Access Control Policy page, select an access control policy for the authentication portal. In this example, we choose .

    ![adfs-access-control-policy.png](/files/EQf2Dos19HmrPN4mxWp0)
17. Click **Next**.
18. In the Ready to Add Trust page, verify that all the setting are correct.

    ![adfs-ready-to-add.png](/files/tlXpMYKrMm3zDhnzFLo7)
19. Click **Next** and then click **Close**.

    ![adfs-finish.png](/files/W4inPGrZ3N5mZ4fcx7ug)
20. [Define the Claim Issuance Policy](/xsoar-6-administrator-guide/6.12/onboard-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).

Return to [Set up ADFS as the Identity Provider Using SAML 2.0](/xsoar-6-administrator-guide/6.12/onboard-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.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.12/onboard-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?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.