{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":40650,"path":"platform-security/authentication/t_ConfigureADFSRelyingParty.md","title":"Configure an ADFS relying party","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure an ADFS relying party\n\nTake the instance metadata and import it into your ADFS server. However, manual configuration of the relying party appears to be easier to implement.\n\n## Before you begin\n\nRole required: sso\\_config\\_admin, business\\_rule\\_admin, script\\_include\\_admin\n\n## Procedure\n\n1.  Navigate to **All** > **Multi-Provider SSO** > **Identity Providers** > **SAML2 Update1** > **Encryption And Signing** and verify that the SAML property Sign AuthnRequest \\(**glide.authenticate.sso.saml2.require\\_signed\\_authnrequest**\\) is not active.\n\n    Only keep this property active if your ADFS administrator can verify that you require signed requests.\n\n2.  Copy the metadata that you generated through the SAML 2 metadata link and save it to a file.\n\n3.  Log into the ADFS server and open the management console.\n\n4.  Select **Relying Party Trusts**.\n\n5.  Select **Add Relying Party Trust** from the top right corner of the window.\n\n    The add wizard appears.\n\n6.  Click **Start** to begin.\n\n7.  Use the **Import File** option to import the metadata file.\n\n8.  Give it a display name such as `ServiceNow` and enter any notes you want.\n\n9.  Select **ADFS 3.0 Profile**.\n\n10. Do not select a token encryption certificate.\n\n    It will use the certificate that is defined on the service that has already been exported. Defining a certificate prevents proper communication with the instance.\n\n11. Do not enable any settings on the **Configure URL**.\n\n12. Enter the instance site to which you connected as the Relying Party trust identifier.\n\n    In this case, use `https://company.service-now.com` and click **Add**.\n\n13. Permit all users to access this relying party.\n\n14. Click **Next** and clear the **Open the Claims when this finishes** check box.\n\n15. Close this page.\n\n    The new relying party trust appears in the window.\n\n16. Right-click on the relying party trust and select **Properties**.\n\n17. Browse to the **Advanced** tab and set the **Secure hash algorithm** as either SHA-256 or SHA-1.\n\n18. Browse to the Endpoints tab and add a **SAML Assertion Consumer** with a **Post** binding and a URL of `https://company.service-now.com/navpage.do`.\n\n\n"}}