...
To set up Security Assertion Markup Language (SAML), we follow this process.
...
Rw ui steps macro | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The Client provides Provide Docupace with the name of the Identity Provider (IDP) (Azure, Ping, OKTA, Auth0, etc.). This allows Docupace to adjust the implementation as needed.
Docupace sets up a SAML site and then sends the site URL to it. From the SAML site, the Customer you can download the Service Provider (SP) Metadata.
The Customer providesProvide Docupace with the following information:
Note: If you need to set up your connection before providing the metadata, the default configuration for a site is
The client_name value may be different if setting up multiple SSO connections.
Site Reliability Engineering (SRE) team at Docupace configures the SAML site with the Identity Provider (IDP) Metadata.
Docupace Business Analyst (BA) creates a test user that the Customer provideslinked to the one that you provided in Step 3.
Docupace informs the Customer you when the SAML setup is complete. Then, Docupace provides the URL for the Service Provider (SP) initiated by the Identity Provider (IDP).
Customer tests You test the SAML integration using the Service Provider URL provided by Docupace.
|
Note |
---|
Troubleshooting: If testing fails after accomplishing all the preferred actions, schedule a meeting between Docupace and the Customer's Identity Prover’s experts. During that meeting, the Customer and Docupace SAML experts will test integration in the real-time environment that can troubleshoot the SAML configuration. As a result, experts will determine whether they need to involve professional services or notDocupace will contact your Identity Provider to troubleshoot it along side their technical experts to adjust the configuration as needed. |