1. Help Center
  2. Email Encryption
  3. Email Encryption - Integration

SAML 2.0 Single Sign On Using Active Directory Federation Services (AD FS) Setup

SAML 2.0 Single Sign-On (SSO) using Active Directory Federation Services (AD FS) Setup Guide

Your Protected Trust Encrypted Email organization can be configured to have users sign-in using a SAML 2.0-compatible identity provider, such as Active Directory Federation Services (AD FS), instead of a having a separate password. This guide is written for AD FS 2.1, however newer versions of AD FS and other identity providers should be similar.

To enable this functionality, an administrator for your organization must follow the steps below. For assistance, please contact the Protected Trust support team.

Step 1) Configure an Identity Provider in Protected Trust

  1. Sign in at https://app.protectedtrust.com/login as an administrator

  2. Navigate to Settings > Single Sign-On & User Sync > Claimed Domains

  3. Ensure that all of your domains are listed. If any are missing, contact our support team to have them added

  4. Navigate to Single Sign-On > Configure New Identity Provider > Configure SSO with SAML 2.0

  5. Enter the SAML federation metadata URL (e.g. https://sts.example.com/FederationMetadata/2007-06/FederationMetadata.xml)

  6. In the field Smart URL, enter something unique to your company (such as your company name without spaces or punctuation)

  7. Set Status set to Enabled (Not Primary)

  8. Click Save

Step 2) Configure Relying Party in AD FS

  1. Open the AD FS console

  2. Click Relying Party Trusts (on the left)

  3. Click Add Relying Party Trust… (on the right)

  4. Click Start on welcome dialog

  5. Select Enter data about the relying party manually and click Next

  6. Enter a Display Name, such as “Protected Trust”, and click Next

  7. Select AD FS profile and click Next

  8. Do not select a token encryption certificate, just click Next

  9. Check Enable support for the SAML 2.0 WebSSO Profile

  10. Go back to the SSO settings in Protected Trust, and copy the value from Assertion Consumer Service Endpoint URL to the clipboard

  11. Go to the AD FS console and paste this value into Relying party SAML 2.0 SSO service URL and click Next

  12. Go back to the SSO settings in Protected Trust, and copy the value from Service Provider ID to the clipboard

  13. Go back to the AD FS console and paste this value into Relying party trust identifier, click Add, then Next

  14. Select Permit all users to access this relying party and click Next

  15. On the Ready to Add Trust page, click Next

  16. Ensure the Open the Edit Claim rules dialog checkbox is marked and click Close

  17. Once the Edit Claim Rules dialog appears, click Add Rule on the Issuance Transform Rules tab

  18. Select Send LDAP Attributes as Claims and click Next

  19. Enter a Claim rule name such as “Name and Email Address”

  20. Select Active Directory as the Attribute store

  21. Add the following entries under Mapping of LDAP attributes:

    a. E-Mail-Addresses → E-mail Address

    b. Given-Name → FirstName (type manually)

    c. Surname → LastName (type manually)

  22. Click Finish

  23. Click OK on the Edit Claim Rules dialog

Step 3) Test Sign In

  1. Open a different browser or private browsing session and navigate to your Smart URL (e.g. https://app.protectedtrust.com/sso/YOUR-SMART-URL)

  2. Follow the steps to sign in. If successful, continue to to Step 4) Enable for the Entire Organization when you’re ready

Step 4) Enable for the Entire Organization

  1. Navigate back to the SSO settings page (Dashboard > Settings > Single Sign-On and User Sync -> Edit)

  2. Change Status to Primary

  3. Click Save

Administrator Tips

How to Bypass SSO Authentication

As an administrator, you can still sign in with the Protected Trust password you previously used, just in case single sign-on stops working for some reason:

  1. Go to https://app.protectedtrust.com/login

  2. Enter your email address

  3. Click the password field and immediately press ESC on your keyboard to cancel the redirect

  4. You can now enter your password and sign in to troubleshoot the SSO issue