Documentation
Introduction

Use this guide to enable 2-Factor Authentication and Single Sign-on (SSO) access via SAML to ITRP.

Prerequisites

1. Have an ITRP account

2. Create a New Realm for the ITRP integration

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 ITRP ID to the SecureAuth IdP Property

For example, add the ITRP ID 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 ITRP

For example, the SP Start URL would be https://company.itrp.com (replace company with actual domain)

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 ITRP 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 ITRP 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/SAML Issuer to the ITRP domain value, e.g. https://company.itrp.com

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

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

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

No configuration is required for the WSFed Reply To/SAML Target URL, SAML Consumer URL, SAML Recipient, or SAML Audience fields

 

12. 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

13. Provide the Domain in order to Download the Metadata File to send to ITRP (if required)

Click Save once the configurations have been completed and before leaving the Post Authentication page

Forms Auth / SSO Token

 

14. 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

ITRP Configuration Steps

 

1. Log into ITRP, click on Settings, then Single Sign-On

2. Set the Remote Logout URL to a URL to where end-users will be redirected after logging out of ITRP, e.g. https://www.google.com

3. Provide IP Addresses that will utilize SecureAuth IdP for authentication, and those not listed will be routed to the normal ITRP login page in the IP Ranges field

Leave this field empty to send all users through SecureAuth IdP authentication

4. Set the SAML SSO URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the realm configured for the ITRP integration, e.g. https://idp.company.com/secureauth2/

5. Provide the Certificate fingerprint (SHA1 fingerprint) of the certificate used in the SecureAuth IdP Web Admin (step 12)

The URLs provided on this ITRP settings page (https://company.itrp.com/access/normal, the Assertion Consumer Service, and the SAML 2.0 Metadata Location) will alter based on the ITRP domain

Troubleshooting / Common Issues

Use https://<domain>.itrp.com/access/normal as a backdoor if there are issues with the SSO, and users are unable to log into the ITRP account.