Blog Archives

Prepare a valid ssl certificate (.pfx file, with private key). This certificate will be used by the ADFS federation service website, so it should be valid with your ADFS website domain name.

Add Active Directory Federation Service Role to the server

On Windows 2016, Open Server Manager, click “Add roles and features”, select “Active Directory Federation Service” on the popup, and press next to install new role.
For more details: visit here

Run ADFS Management tool from Service Manger.

Click “Certificates”, import your certificate to ADFS service.

On ADFS Management, Click “Add Relying Party Trust”

Select “Claims aware” on the wizard popup, and click “Next”

Select “Enter data about the relying party manually” and click “Next”

Input “www.securedsigning.com” in the “Display name” and click “Next”

Browse to your certificate to import certificate and click “Next”

Enable both WS-Federation Passive protocol and SAML 2.0 WebSSO protocol. For both protocols input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as endpoints and click “Next”

Input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as identifiers and click “Next”

Please notice that the rely party identifier is case sensitive. Please input the exact value.

Select the “Permit all users to access this relying party” option and click “Next”

Click “Next” and “Close”

Select new added Relying party trust “www.securedsigning.com”, click “Edit Claim Issuance Policy…”

click “Add Rule…”

In the popup wizard, select “Send LDAP Attributes as Claims” and click “Next”

Input the rule name, select “Active Directory” as the Attribute store and select the LDAP attributes below:

        E-Mail-Address   -> E-Mail Address
        Surname -> Surname
        Given-Name -> Given Name
        User-Principal-Name -> Windows account Name

Click “Finish”