Documentation
Introduction

Use this guide to enable 2-Factor Authentication and Single Sign-on (SSO) access via SAML to Ultipro using AD FS 2.0.

Prerequisites

1. Have an Ultipro account with AD FS 2.0

2. Create a New Realm for the Ultipro integration in the SecureAuth IdP Web Admin

3. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined
  • Data – an enterprise directory must be integrated with SecureAuth IdP
  • Workflow – the way in which users will access this application must be defined
  • Registration Methods – the 2-Factor Authentication methods that will be used to access this page (if any) must be defined
SecureAuth IdP Configuration Steps
Data

 

1. In the Profile Fields section, map the directory field that contains the user's Ultipro ID to the SecureAuth IdP Property

For example, add the Ultipro ID Field to the Email 2 Property if it is not already contained somewhere else

Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Workflow

 

2. In the SAML 2.0 Service Provider section, provide the SP Start URL to enable SSO and to redirect users appropriately to access Ultipro

For example, the SP Start URL would be https://company.ultipro.com

Click Save once the configurations have been completed and before leaving the Workflow page to avoid losing changes

Post Authentication

 

3. Select SAML 2.0 (SP Initiated) Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin

4. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/SAML20SPInit.aspx)

5. A customized post authentication page can be uploaded, but it is not required

User ID Mapping

 

6. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Ultipro ID (Email 2)

7. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if Ultipro requires it, which the Service Provider (SP) will provide

8. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation

 

9. Set the WSFed Reply To/SAML Target URL to https://efs.ultipro.com/adfs/ls/

10. Set the SAML Consumer URL to https://efs.ultipro.com/adfs/ls/

11. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Ultipro

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Ultipro side

12. Set the SAML Recipient to https://efs.ultipro.com/adfs/ls/

13. Set the SAML Audience to https://efs.ultipro.com/adfs/services/trust

14. Set the SAML Offset Minutes to make up for time differences between devices

15. Set the SAML Valid Hours to limit for how long the SAML assertion is valid

 

16. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, click Select Certificate and choose the appropriate certificate

17. Download the Assertion Signing Certificate, which will be used in the Ultipro Configuration Steps

Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

 

18. Click View and Configure FormsAuth keys / SSO token to configure the token/cookie settings and to configure this realm for SSO

These are optional configurations


 To configure this realm's token/cookie settings, follow these steps:
Forms Authentication


1. If SSL is required to view the token, select True from the Require SSL dropdown

2. Choose whether SecureAuth IdP will deliver the token in a cookie to the user's browser or device:

  • UseCookies enables SecureAuth IdP to always deliver a cookie
  • UseUri disables SecureAuth IdP to deliver a cookie, and instead deliver the token in a query string
  • AutoDetect enables SecureAuth IdP to deliver a cookie if the user's settings allow it
  • UseDeviceProfile enables SecureAuth IdP to deliver a cookie if the browser's settings allow it, no matter the user's settings

3. Set the Sliding Expiration to True if the cookie remains valid as long as the user is interacting with the page

4. Set the Timeout length to determine for how many minutes a cookie is valid

No configuration is required for the Name, Login URL, or Domain fields

Machine Key

5. No changes are required in the Validation field, unless the default value does not match the company's requirement

If a different value is required, select it from the dropdown

6. No changes are required in the Decryption field, unless the default value does not match the company's requirement

If a different value is required, select it from the dropdown

No configuration is required for the Validation Key or Decryption Key fields

Authentication Cookies

 

7. Enable the cookie to be Persistent by selecting True - Expires after Timeout from the dropdown

Selecting False - Session Cookie enables the cookie to be valid as long as the session is open, and will expire once the browser is closed or the session expires

No configuration is required for the Pre-Auth Cookie, Post-Auth Cookie, or the Clean Up Pre-Auth Cookie fields

Click Save once the configurations have been completed and before leaving the Forms Auth / SSO Token page to avoid losing changes

To configure this realm for SSO, refer to SecureAuth IdP Single Sign-on Configuration

To configure this realm for Windows Desktop SSO, refer to Windows Desktop SSO Configuration Guide

Ultipro Configuration Steps
Set up AD FS 2.0 with Claims Provider Trust

1. To set up AD FS 2.0 with a Claims Provider Trust, open the Claims Provider Trust Wizard

2. In the Select Data Source section, select Enter claims provider trust data manually from the options, and click Next

 Click here to expand...

 

3. In the Specify Display Name section, provide a Display Name, and click Next

 Click here to expand...

 

4. In the Choose Profile section, select AD FS 2.0 profile from the options, and click Next

 Click here to expand...

 

5. In the Configure URL section, check Enable support for the SAML 2.0 WebSSO protocol; set the Claims provider SAML 2.0 SSO service URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the SecureAuth IdP Ultipro-integrated realm (e.g. https://secureauth.company.com/secureauth1/); and click Next

Make sure to include the trailing slash "/" at the end of the URL to avoid IIS errors

 Click here to expand...

 

6. In the Configure Identifier section, set the Claims provider trust identifier to the same Unique Name established in the WSFed/SAML Issuer field in the SecureAuth IdP Web Admin (step 11), and click Next

 Click here to expand...

 

7. In the Configure Certificates section, click Add to upload the Assertion Signing Certificate from the SecureAuth IdP Web Admin (step 17), and click Next

 Click here to expand...

 

8. In the Ready to Add Trust section, verify that the settings are correct, and click Next

 Click here to expand...

 

9. In the Finish section, click Close to complete the wizard

 Click here to expand...

 

AD FS 2.0 Management Console

 

10. Open the AD FS 2.0 Management Console, and browse to the new Claims Provider Trust

11. Open it and verify the settings

Specifically:

In the Identifiers tab, the Claims provider identifier must match the WSFed/SAML Issuer value in the SecureAuth IdP Web Admin (step 11)

 Click here to expand...

 

In the Certificates tab, the Assertion Signing Certificate from the SecureAuth IdP Web Admin (step 17) should be present and show trust all the way up to the root

Downloading and installing the root certificates into the AD FS 2.0 server certificate store may be required

 Click here to expand...

In the Endpoints tab, the SAML Single Sign-On Endpoints must point to the SecureAuth IdP Ultipro-integrated realm (https://secureauth.company.com/secureauth1/), and it must be a SAML Redirect endpoint

 Click here to expand...

In the Advanced tab, the Secure hash algorithm must be SHA-1 if the certificate is SHA-1; or must be SHA-256 if the certificate is SHA-256

In the General section of the Certificate window, the type of certificate is expressed

 Click here to expand...

 

Avoid ID4037 Error

To avoid the ID4037 error in AD FS 2.0 that hinders the communication from working due to not being able to check the SecureAuth IdP SSL certificate against a CRL, run the following commands from a Windows PowerShell window on the AD FS 2.0 server:

  • Add-PSSnapin Microsoft.Adfs.Powershell
  • Set-ADFSClaimsProviderTrust -TargetName "company.com" -SigningCertificateRevocationCheck "None"

Be sure to replace the company.com value with the actual Display Name created in step 3

 Click here to expand...

 

Click here for more information