To securely use SAML Metadata, partners share metadata which that contains:
Entity ID
Cryptographic Keys
Protocol Endpoints (bindings and locations)
| Tip |
|---|
Tips:
|
...
The Assertion Consumer URL is different and is provided in the metadata XML file. The metadata XML can either be imported into your IDP or configured manually. If you need to configure it manually, the table below lists common mapping. Your IDP likely has instructions on how to manually configure SAML connections in their system. If you use OKTA, click here.
...
Link Type | Purpose | Link |
|---|---|---|
Base | For configuring Service Provider (SP) initiated by SSO | |
Deep | For launching the Monitor function | Non-SSO URL - https://{{host}}/site_ui#/monitor |
SSO URL - https://{{host}}/site_ui/sso/saml/default/bookmark/monitor |
Troubleshooting
You can solve two kinds of errors. If you see any other errors, you will need to contact Support.
Action Not Found
The Action Not Found error means that you entered the incorrect Assertion Consumer Service URL to the URL that contains the Metadata. You can find the correct URL in the metadata XML file.
No valid subject assertion found in response
If you see No valid subject assertion found in response, it means that the certificate configured in Docupace does not match the certificate configured in your IDP. This means you need to update the Docupace metadata configuration. This can occur if there is a mixup between environments or if the IDP configuration has changed since Docupace received the metadata.
