Page Comparison

...

Finally, you need to configure the Identity Server to act as the Single Sign-on provider. Each relying party should be registered as a service provider at the Identity Server-end. The following is a sample configuration for registering a Carbon server as a service provider.

1. Specify the " Issuer. " This should be equal to the ServiceProviderID value mentioned in the authenticators.xml of the relying party Carbon server.
2. Specify the " Assertion Consumer URL. " This is the URL to which the browser should be redirected after the authentication is successful. It should have this format: https://(host-name):(port)/acs.
3. Select Use fully qualified username in SAML Response if that feature is required.
4. Select " Enable Response Signing to sign the SAML2 Responses returned after the authentication.
5. Select Enable Assertion Signing" to  to sign the SAML2 Assertions returned after the authentication. SAML2 relying party components expect these assertions to be signed by the Identity Server.
6. Select " Enable Signature Validation in Authentication Requests and Logout Requests if you need this feature configured.
7. Select Enable Single Logout" so  so that all sessions will be are terminated once the user signs out from one server.
   Image Removed. You can enter a Custom Logout URL if required.
8. Select Enable Attribute Profile to enable this and add a claim by entering the claim link and clicking the Add Claim button.
9. Select Enable Audience Restriction to restrict the audience. You may add audience members using the Audience text box and clicking the Add Audience button.
   Image Added