All Collections
SSO for Envoy via Microsoft Active Directory
SSO for Envoy via Microsoft Active Directory

Learn how to set up SAML using ADFS.

Updated over a week ago

Configuring SAML for ADFS 3.0

This guide does not cover how to install ADFS, configure domains and certificates, or provision users in AD or Envoy.

Before you configure ADFS for SSO with Envoy:

Users should already exist in Active Directory, and the admins and employees that need Envoy access should already exist in Envoy. If you need help populating your Envoy employee directory from AD, learn more here.

This guide also assumes ADFS v3.0 or ADFS 2012 R2 are installed on Windows Server 2012 R2.

Step 1: Configure ADFS

  1. Go to the ADFS Management Console.

  2. Under Trust Relationships, select “Relying Party Trusts,” then “Add Relying Party Trust”. Envoy will be the relying party in this setup.

  3. Under Select Data Source, select “Import data about the relying party published online or on a local network”.

    1. In the Federation metadata address field, type in:

  4. For Display Name enter “Envoy Identity” (you can enter any name you like here to identify the service).

    1. Click “Next” and select “ADFS profile,” then click “Next” again.

  5. Click through the remaining steps, configuring Multi-factor Authentication and Issuance Authorization Rules as desired.

    1. These are not required, and this guide assumes they are not used.

  6. After finishing the wizard, select Envoy Identity and then “Edit Claim Rules” (alternatively, you can leave the box checked at the end of the wizard to automatically open the claim rules).

  7. At this point, there should not be any rules. Select the option to add a rule.

  8. Under Claim rule template, select “Send LDAP Attributes as Claims” from the dropdown.

  9. Click “Next.”

  10. Under Claim rule name enter “Get LDAP email” (you can enter any name you like here).

  11. For Attribute store, select “Active Directory”. Add a mapping by selecting “E-Mail Addresses” from both the LDAP Attribute and Outgoing Claim Type drop-downs.

    1. This assumes that your Envoy login email is stored in Active Directory as the user’s Email Address attribute.

    2. If you intend to use a different attribute, change the first field to the attribute that contains the user’s login for Envoy.

  12. Click “Finish”.

  13. Click “Add” to create a second Claim Rule.

  14. On the next page, select “Transform an Incoming Claim”.

  15. Under Claim rule name, enter something such as “Email to NameID”.

    1. For incoming claim type, select “E-Mail Address” (this corresponds to the Outgoing Claim from the previous rule).

    2. For outgoing claim type, select “Name ID”.

    3. For outgoing name ID format, select “Email”.
      • Leave the other options on their defaults.

    4. Click “Finish” then save the rules by clicking “Apply” or “OK”.

Step 2: Configuring Envoy

Envoy requires a fingerprint of the authentication certificate that will be used to sign the SAML assertion. In this section, we’ll find the fingerprint and connect with Envoy.

  1. In the management console, under Service > Certificates, find the “Token-signing” certificate.

  2. Envoy expects a SHA1 fingerprint. On the Details tab, scroll down to see that the Thumbprint Algorithm is SHA1, then select “Thumbprint” to view the signature.

  3. Copy this thumbprint.

  4. Log in to your Envoy dashboard and go to Apps > All Apps > Directory and SSO > Directory Settings> SAML> Click install

  5. Paste the thumbprint that was copied from AD into the "Fingerprint" field.

    1. Note: be sure to remove all the spaces from your fingerprint.

  6. Under Identity Provider HTTP SAML URL you can optionally enter the URL for the IdP that corresponds to Envoy.

    1. This may be something like

  7. Click “Save”.


If you’re logged in to Envoy, log out now. This will ensure that any errors are not hidden during login.

  1. Login to the AD IdP-initiated SignOn page.

  2. Select “Envoy” from the dropdown, and click “Sign in”.

If everything is configured correctly, you should be logged in to the Envoy dashboard!

Did this answer your question?