Documentation
Introduction

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

Prerequisites

1. Have a ShareFile account and access to admin console

2. Create a New Realm in the SecureAuth IdP Web Admin for the ShareFile 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 ShareFile ID to the SecureAuth IdP Property

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

Post Authentication

 

2. Select SAML 2.0 (SP Initiated) 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/SAML20SPInit.aspx)

User ID Mapping

 

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

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

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

SAML Assertion / WS Federation

 

6. Set the SAML Consumer URL to https://<company>.sharefile.com/saml/acs, and replace <company> with the actual hostname

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

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

8. Provide the SP Start URL to enable SSO and to redirect users appropriately to access ShareFile

For example, the SP Start URL would be https://company.sharefile.com/saml/login

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

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

The exact SAML Consumer URL and SP Start URL values can be found in the ShareFile admin console, in the Configure Single Sign-on section

Refer to the ShareFile Configuration Steps below for more information

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

 

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

12. Download the Assertion Signing Certificate, which is used in the ShareFile 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

 

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

ShareFile Configuration Steps

 

1. Log into the ShareFile admin console, and select Configure Single Sign-On from the menu

2. Check to Enable SAML

3. Set the ShareFile Issuer / Entity ID and Your IDP Issuer / Entity ID to the same Unique Name set in the SecureAuth IdP Web Admin (step 7)

4. Click Change to upload the Assertion Signing Certificate from the SecureAuth IdP Web Admin (step 12) as the X.509 Certificate

5. Set the Login URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the ShareFile-integrated realm, e.g. https://secureauth.company.com/secureauth2/

6. Click Save

*** The URLs provided at the top of this page correspond to the SAML Consumer URL and SP Start URL values required in the SecureAuth IdP Configuration Steps

  • No labels