Documentation
Introduction

Use this guide to enable Service Provider (SP)-initiated Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to DocuSign.

For SecureAuth IdP-initiated access, refer to DocuSign (IdP-initiated) Integration Guide

Prerequisites

1. Obtain a DocuSign account with administrator permissions

2. Create a New Realm for the DocuSign 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 Multi-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 first name to the First Name Property – e.g. givenname

2. Map the directory field that contains the user's last name to the Last Name Property – e.g. surname

3. Map the directory field that contains the user's email address to the Email 1 Property – e.g. emailaddress

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

Workflow

 

4. In the SAML 2.0 Service Provider section, provide the SP Start URL to enable SSO and to redirect users to the DocuSign login page

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

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

Post Authentication

 

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

User ID Mapping

 

6. Select the SecureAuth IdP Property that corresponds to the directory field that contains the DocuSign Name ID – e.g. Authenticated User ID

7. Select urn:oasis:names:tc:SAML:2.0:nameid-format:persistent from the Name ID Format dropdown

8. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation

 

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

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

10. Set the SAML Offset Minutes to accommodate any time differences between devices

11. Set the SAML Valid Hours to limit the length of time for which 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 a third-party certificate is used for the SAML assertion

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

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

SAML Attributes / WS Federation

 

14. Set the Name of Attribute 1 to emailaddress

15. Set the Namespace (1.1) to http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

16. Select Email 1 from the Value dropdown

17. Set the Name of Attribute 2 to surname

18. Set the Namespace (1.1) to http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

19. Select Last Name from the Value dropdown

20. Set the Name of Attribute 3 to givenname

21. Set the Namespace (1.1) to http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

22. Select First Name from the Value dropdown

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

Forms Auth / SSO Token

 

23. (OPTIONAL) Click View and Configure FormsAuth keys / SSO token to configure the token/cookie settings and to configure this realm for SSO

 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

DocuSign Configuration Steps

 

1. Log on the DocuSign Admin application as an administrator and click Identity Providers

2. In the Identity Provider view, click ADD IDENTITY PROVIDER

3. Set SecureAuthIdP as the Name of the Identity Provider

4. Set the Identity Provider Issuer to the Unique Name entered in step 9 of the SecureAuth IdP Configuration Steps

5. Set the Identity Provider Login URL to the entire URL address which includes the realm name – e.g. https://secureauthFQDN/SecureAuth{realm#}/SecureAuth.aspx

6. Set Send AuthN request by the POST method

7. Set Send Logout request by the POST method

8. Click SAVE

Refer to DocuSign's Identity Providers document for more information on configuring the DocuSign Identity Provider page