Configure ADFS as SAML Identity Provider
Create a custom SAML connection to Microsoft's Active Directory Federation Services (ADFS) to get more flexibility when configuring your mappings. To create the custom connection, you will need to:
Create a SAML connection where Auth0 acts as the service provider.
Edit the Relying Party Trust in ADFS.
Enable and test your integration.
Add Relying Party Trust
Create using federation metadata
Follow the steps on Create a claims aware Relying Party Trust using federation metadata (MSDN). For the Federation metadata address in Step 4, the URL you enter should be in one of these formats:
Once you've finished creating the relying party trust, continue to the next section.
Launch your instance of ADFS and start the Add Relying Party Trust wizard.
On the Welcome page, choose Claims aware and click Start.
On the Select Data Source page, select Enter data about the relying party manually and click Next.
On the Specify Display Name page, provide a descriptive name for your relying party (the typical format is
urn:auth0:YOUR_TENANT:YOUR_CONNECTION_NAME) and a brief description under Notes. Be sure to replace
YOUR_CONNECTION_NAMEwith a unique name you will also use to create a connection in Auth0 in a later step. If you are unsure of the connection name at this time, you can always edit the connection name later. Click Next.
On the Configure Certificate page, click Next. (We will come back to configure the certificate later.)
On the Configure URL page, check the box for Enable support for the SAML 2.0 WebSSO protocol. The wizard then asks for a Relying party SAML 2.0 SSO service URL. For the time being, provide a placeholder URL; we will return to this step later. Click Next.
On the Configure Identifiers page, indicate that the Relying party trust identifier is
urn:auth0:YOUR_TENANT:YOUR_CONNECTION_NAME(or whatever value you used as the display name when you started using the wizard). Click Next.
On the Choose Access Control Policy page, select Permit everyone and click Next.
Review the settings you provided on the Ready to Add Trust page and click Next to save your information. If you were successful, you'll see a message indicating that on the Finish page.
Make sure that the Configure claims issuance policy for this application checkbox is selected, and click Close.
Edit Claim Issuance Policy
After you close the Add Relying Party Trust wizard, the Edit Claim Issuance Policy window appears.
Click Add Rule... to launch the wizard.
Select Send LDAP Attributes as Claims for your Claim rule template, and click Next.
Provide a value for the Claim rule name, such as "LDAP Attributes" (it can be anything you want).
Choose Active Directory as your Attribute Store.
Map your LDAP attributes to the following outgoing claim types:
LDAP Attribute Outgoing Claim E-Mail-Addresses E-Mail Address Display-Name Name User-Principal-Name Name ID Given-Name Given Name Surname Surname
Name IDoutgoing claim should always be present to ensure correct session handling. We strongly recommend adding all of the claims listed above, especially
E-Mail Address, since they are the ones most commonly used. You can add additional claim mappings if necessary.
In the Edit Claim Issuance Policy window, click Apply. You can now exit out of this window.
Export Signing Certificate
Finally, you'll need to export the signing certificate from the ADFS console to upload it to Auth0.
Using the left-hand navigation pane, go to ADFS > Service > Certificates. Select the Token-signing certificate, and right click to select View Certificate.
On the Details tab, click Copy to File.... This launches the Certificate Export Wizard. Click Next.
Choose Base-64 encoded X.509 (.CER) as the format you'd like to use. Click Next.
Provide the location to where you want the certificate exported. Click Next.
Verify that the settings for your certificate are correct and click Finish.
Create SAML connection with Auth0 as service provider
Follow the tutorial on creating a SAML connection where Auth0 acts as the service provider. Where prompted, upload the signing certificate you exported from ADFS.
The sign in and sign out URLs are usually in the form of
Click Save. A page with instructions for creating a new Relying Party Trust in ADFS appears displaying the exact values required for your Auth0 account/connection. Make a note of these values. Here is an example:
Parameter Example Value Post-back URL
https://<YOUR CUSTOM DOMAIN>/login/callback?connection=YOUR_CONNECTION_NAMEif a custom domain is configured
https://YOUR_DOMAIN/login/callback?connection=YOUR_CONNECTION_NAMEif not using custom domains
Edit Relying Party Trust
In the ADFS console, go to ADFS > Relying Party Trusts using the left-hand navigation pane. Select the Relying Party Trust you created earlier and click Properties (located on the right-hand navigation pane).
Select the Identifiers tab, and populate the Relying Party Identifier with the Entity ID value from the previous screen. Be sure to click Add to add the identifier to your list.
Select the Endpoints tab, and select the placeholder URL you provided earlier. Click Edit....
Populate the Trusted URL with the Post-back URL value.
Click OK. Finally, click Apply and exit the Properties window.
Enable sign requests (optional)
Optionally, you can sign your SAML requests to the ADFS server.
Go to the Settings page for your SAML-P Identity Provider in the Auth0 Dashboard.
Enable Sign Requests.
Just below the Sign Requests toggle is a link to download your certificate.
Return to ADFS and load the downloaded certificate using the Signatures tab of the Relying Party properties dialog.
Enable and test the integration
Before you test your integration, make sure that you've completed the following steps:
Create a user on the identity provider that you can use to test your new connection.
Enable your Connection for at least one application.
Select the connection that you want to test and click the ellipses (...) then click Try. The Microsoft Sign in screen will appear. Sign in and click Next.