Skip to main content

EchoSign (IdP-initiated) Integration Guide


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


1. Have an EchoSign account

2. Create a New Realm for the EchoSign 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

  • 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



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

For example, add the EchoSign 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 (IdP 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/SAML20IdPInit.aspx)

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

User ID Mapping


5. Select the SecureAuth IdP Property that corresponds to the directory field that contains the EchoSign 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 EchoSign requires it, which the SP will provide

7. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation


8. Set the WSFed Reply To/SAML Target URL to https://<company>

9. Set the Consumer URL to https://<company>

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

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

11. Set the SAML Recipient to https://<company>

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

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


No configuration is required for the SAML Audience or SP Start URL fields


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

15. Download the Assertion Signing Certificate, which will be used in the EchoSign Configuration Steps


Click Save once the configurations are 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.


EchoSign Configuration Steps


1. Log into the EchoSign admin console, and select SAML Settings under Account Settings

2. Select SAML Allowed - users may use SAML but can continue using their EchoSign credentials from the SAML Mode options

3. Set the IdP Entity ID to the same Unique Name established in the WSFed/SAML Issuer field in the SecureAuth IdP Web Admin (step 10)

4. Set the IdP Login URL to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the SecureAuth IdP EchoSign-integrated realm, e.g.

5. Set the IdP Logout URL to any URL to where users will be redirected upon logging out of EchoSign

6. Copy the content of the Assertion Signing Certificate from the SecureAuth IdP Web Admin (step 15) and paste it into the IdP Certificate field

7. Note the SP assertion consume URL and the SP Log in URL for proper SecureAuth IdP configuration

8. Click Save Changes