Add SV3 Enterprise as a relying party trust in Active Directory Federation Services (ADFS) so your ADFS server accepts Single Sign-On (SSO) requests from SV3 Enterprise.
Before you start
- You need administrator access to the Active Directory server that runs ADFS.
- Have the SV3 Enterprise metadata file on that server. See how to turn on SSO in SV3 Enterprise.
- These steps are for ADFS on Windows Server 2016 and later. If you use Windows Server 2012 R2, Relying Party Trusts is under AD FS > Trust Relationships, and the wizard has no Claims aware choice. In place of step 8, select I do not want to configure multi-factor authentication settings for this relying party trust at this time, click Next, then select Permit all users to access this relying party, and click Next. On the final page, the option is Open the Edit Claim Rules dialog for this relying party trust when the wizard closes.
Steps
- On the ADFS server, open AD FS Management. In Server Manager, select Tools > AD FS Management, or search for it from the Start menu.
- In the left pane, expand AD FS, and then select Relying Party Trusts.
- In the Actions pane, click Add Relying Party Trust....
- On the Welcome page, select Claims aware, and then click Start.
- On the Select Data Source page, select Import data about the relying party from a file.
- Enter the path to the SV3 Enterprise metadata file, or browse to it, and then click Next. If a message says some content was skipped, click OK.
- In Display Name, enter a name for the trust, for example
SV3 Enterprise. You can also add Notes. Click Next. - On the Choose Access Control Policy page, select Permit everyone, and then click Next.
- On the Ready to Add Trust page, review the settings imported from the SV3 Enterprise metadata on each tab, and then click Next.
- On the Finish page, make sure Configure claims issuance policy for this application is selected.
- Click Close.
Result
SV3 Enterprise is listed as a relying party trust, and the Edit Claim Rules dialog opens. Next, add a transform claim rule.
Comments
0 comments
Article is closed for comments.