Skip to main content

Central Desktop (SP-initiated) Integration Guide

Introduction

Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Central Desktop.

Prerequisites

1. Have a Central Desktop account

2. Provide the company email domain for the Central Desktop representative for proper account provisioning

3. Create a New Realm for the Central Desktop integration

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

  • Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined

SecureAuth IdP Configuration Steps

Data

44831864.png

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

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

Warning

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

Post Authentication

44831869.png

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

3. 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/SAML20SPInitPost.aspx)

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

User ID Mapping

60564688.png

5. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Central Desktop ID (Email 2)

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

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

7. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation

44831865.png

8. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Central Desktop

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

9. Provide the SP Start URL to enable SSO and to redirect users appropriately to access Central Desktop

For example, the SP Start URL would be https://[company].centraldesktop.com/login

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

Note

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

70489017.png

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 Central Desktop (if required)

Warning

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

Forms Auth / SSO Token

Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.

44833086.png

Central Desktop Configuration Steps

44831870.png

1. Log into the Central Desktop Admin Console

2. Click Account, then Company Setup in the top right corner

3. Click the Advanced tab

4. Click Single Sign On

5. In the Single Sign On Settings, check Enable SAML v2 Single Sign On

6. Set the SSO URL (aka SAML Issuer / ID URL / etc) to the same value provided in the Issuer field in the SecureAuth IdP Web Admin

7. Set the SSO Login URL to the SecureAuth IdP Central Desktop configured realm (e.g. https://secureauth.company.com/secureauth12/secureauth.aspx)

8. Set the SSO Logout URL to any URL to which users will be redirected upon signing out

9. Provide the SSO Certificate Fingerprint, which is configured in the SecureAuth IdP Central Desktop realm

10. Click Update