How To: Use AD FS as the IdP for SSO

To use AD FS as the identity provider for single sign-on, you must complete two steps. First, you must configure your AD FS server to recognise Civica Learning as a relying party, and then secondly, you must provide Civica Learning with details of your AD FS configuration (federation metadata), to enable us to complete the integration.

Relying party configuration

Please follow the instructions below to configure your AD FS server for integration with our platform:

https://auth0.com/docs/connections/enterprise/adfs

To complete the process on this page you will require the following information:

Note: customername.eu / eu:customername in the information below will vary and we will need to provide this. Please contact the Support or Implementation team for this information before you start the configuration process. 

• If using the scripted setup, you will need to use the following options:
  • Realm Identifier: urn:auth0:eu:customername
  • Endpoint: https://customername.eu.auth0.com/login/callback

• If using the manual steps, you will need the following information to complete the process:
  • Step 5
    • The name for the application can be anything of your choosing, but we suggest using a name which clearly identifies this relying party as being used by your lms such as the lms name.
  • Step 8
    • The Relying Party WS-Federation Passive protocol URL is https://customername.eu.auth0.com/login/callback
  • Step 9 
    • The Relying party trust identifier is urn:auth0:eu:customername (this must be added in addition to the default relying party)
  • Step 16
    • In most scenarios this can be omitted. If his is required for your configuration then the support team will discuss this with you at the appropriate time.

Federation metadata

After you have configured the relying party on your AD FS server, you need to provide the support team with either:

• The address of you AD FS server.
  • This option is preferred and should be used when federation metadata is exposed by your AD FS server.
  • Updates can automatically be retrieved when signing certificates are updated.
• A federation metadata file exported from your AD FS server.
  • This option is available if your AD FS server does not expose federation metadata.
  • Federation metadata must be manually updating by sending the support team an updated federation metadata file each time the signing certificates change.

After both of these steps are complete, the Civica Learning support team will complete the configuration using the details provided.