Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To securely use SAML Metadata, partners share metadata which contains:

  • Entity ID.

  • Cryptographic Keys.

  • Protocol Endpoints (bindings and locations).

Tip

Tips:

  • Every SAML System Entity contains entity ID, the globally-unique identifier (used in software configurations), relying-party databases, and client-side cookies. On the wire, every SAML Protocol message contains the entity ID of the issuer.

  • SAML Metadata can be identified by the initial tag: <md <md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" ...>

Connect Metadata Location

...

IDP Setup

Docupace provides SAML Metadata, which you can use to set up the site 2.0 Metadata. Your Identity Provider (IDP) administrator can use this metadata to register Docupace as an authorized Service Provider (SP). Also, you can accomplish this process by importing the metadata provided by Docupace into Identity Provider (IDP).

Tip

Tips:

  • To import metadata into your Identity Provider (IDP), refer to your IDP documentation.

  • To finalize the setup, provide Docupace with Identity Provider (IDP) and IDP's metadata.

...

  • SAML assertion should contain <saml:Subject><saml:NameID>userNameInDocupace<saml:NameId/></saml:Subject>

  • userNameInDocupace must match exactly the configured user in Docupace.

...

Docupace supports a Service Provider (SP) that is initiated by SSO. This Service Provider (SP) initiated by SSO includes the following link types:

Link Type

Purpose

Link

Base

For configuring Service Provider (SP) initiated by SSO

https://{{host}}/site_ui/sso/saml/default

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