Security Token Service and Tridion Docs

Tridion Docs integrates with a Security Token Service to externalize authentication and to provide a Single Sign-On experience across all Tridion Docs components.

For a successful integration, the Security Token Service must support specific protocols and token formats.

The following protocol requirements for a Security Token Service are based on active or passive profile categories.

Passive profile protocol requirements
WS Federation
Active profile protocol requirements
WS Trust 1.3
Part of WS Trust 1.4. Only the part that specifies the ActAs element is required to support identity delegation.

The Security Token Service is required to generate security tokens using the SAML 1.1 format.

The following diagram shows all required client connections for the Tridion Docs Federated services. The arrow captions provide information about the schema (HTTP or HTTPS) and the dependent protocol or technology in use.

DD: Dynamic Delivery.