Adding AD FS Authentication
with AD FS and SAML
TechSmith supports single sign-on (SSO) authentication through SAML 2.0. A SAML 2.0 identity provider (IdP) can take many forms, one of which is a self-hosted Active Directory Federation Services (AD FS) server. AD FS is a service provided by Microsoft as a standard role for Windows Server that provides a web login using existing Active Directory credentials.
To use AD FS to log into a TechSmith service like TechSmith Relay, you will need the following components:
- An Active Directory instance where all users have a uniquely specified username attribute.
- An Active Directory instance where all users have an email address attribute.
- A server running Microsoft Server 2012 or 2008. This guide uses screenshots from Server 2012R2, but similar steps should be possible on other versions.
- A SSL certificate to sign your AD FS login page and the Signing Certificate for that certificate.
- An installed certificate for hosted SSL.
After meeting these basic requirements, you must have AD FS installed on your server. Instructions for configuring and installing AD FS can be found here. (Instructions can also be found here.)
In your AD FS installation, please note the value for the 'SAML 2.0/W-Federation' URL in the AD FS Endpoints section. If you chose the defaults for the installation, this will be '/adfs/ls/'.
If you're already comfortable setting up and configuring AD FS, go ahead and skip ahead to Step 4 - Configuring TechSmith ID to work with AD FS.
Step 1 - Adding a Relying Party Trust
At this point you should be ready to set up the AD FS connection with TechSmith. The connection between AD FS and TechSmith is defined using a Relying Party Trust (RPT).
Select the Relying Party Trusts folder from AD FS Management, and add a new Standard Relying Party Trust from the Actions sidebar. This starts the configuration wizard for a new trust.
- In the Select Data Source screen, select the last option, Enter Data About the Party Manually.
- On the next screen, enter a Display Name that you'll recognize in the future, and any notes you want to make.
- On the next screen, select the AD FS FS profile radio button.
- On the next screen, leave the certificate settings at their defaults unless you would like to choose a certificate in which case you'll have to provide your public key later.
- On the next screen, check the box labeled Enable Support for the SAML 2.0 WebSSO protocol. The service URL will be
- On the next screen, add a Relying party trust identifier of
- On the next screen, you may configure multi-factor authentication but this is beyond the scope of this guide.
- On the next screen, select the Permit all users to access this relying party radio button.
- On the next two screens, the wizard will display an overview of your settings. On the final screen use the Close button to exit and open the Claim Rules editor.
Step 2 - Creating claim rules
Once the relying party trust has been created, you can create the claim rules and update the RPT with minor changes that aren't set by the wizard. By default the claim rule editor opens once you created the trust.
- To create a new rule, click on Add Rule. Create a Send LDAP Attributes as Claims rule.
- On the next screen, using Active Directory as your attribute store, do the following:
- From the LDAP Attribute column, select E-Mail Addresses.
- From the Outgoing Claim Type, select E-Mail Address.
- Click on OK to save the new rule.
- Create another new rule by clicking Add Rule, this time selecting Transform an Incoming Claim as the template.
- On the next screen:
- Select [A unique, un-changing value] as the Incoming Claim Type.
- For Outgoing Claim Type, select Name ID.
- For Outgoing Name ID Format, select Name ID.
- Leave the rule to the default of Pass through all claim values.
- Finally, click OK to create the claim rule, and then OK again to finish creating rules.
Step 3 - Adjusting the trust settings
You still need to adjust a few settings on your relying party trust. To access these settings, select Properties from the Actions sidebar while you have the RPT selected.
- In the Endpoints tab, click on add SAML to add a new endpoint.
- For the Endpoint type, select SAML Logout.
- For the Binding, choose POST.
- For the Trusted URL, create a URL using:
- The web address of your AD FS server
- The AD FS SAML endpoint you noted earlier
- The string
- The URL should look something like this:
- Confirm you changes by clicking OK on the endpoint and the RPT properties. You should now have a working RPT for TechSmith.
Step 4 - Configuring TechSmith ID to work with AD FS
The claim types that can be configured for use within TechSmith Relay are the following:
- Email (required)
- User ID (required and must be globally unique in your IDP)
- First Name
- Last Name
- Display Name (recommended)
After setting up AD FS, you need to configure your TechSmith instance to authenticate using SAML. To do this you will need to create a basic TechSmith ID (if you don't already have one) and login to http://myaccount.techsmith.com.
Through a conversation with TechSmith personnel, you must be granted access to your organization's setup of your Identification provider. When this is done, you will see an Admin link at the top of the page.
Click the Add Provider button. Choose SAML 2 from the dropdown list. You'll use your full AD FS server URL with the SAML endpoint as the SSO URL, and the login endpoint you created as the logout URL. The signing certificate will be of the certificate installed in your AD FS instance.
Following the saving of data in this page you will be presented with the following information from TechSmith:
- Provider Name
- Assertion Consumer URL
Step 5 - Test the Integration
Test the integration by attempting to login to the application and confirm that the application recognizes your user and has the right attributes/claims associated.
You should now have a working AD FS SSO implementation for your TechSmith Relay instance.