SAML Technical Requirements

Supported SAML Technologies

Thomson Reuters Legal uses a third party SSO solution called PingFederate Server from PingIdentity to handle Federated Single Sign-On internally and externally. PingFederate supports three Single Sign-On standards:
  • SAML 1.x and SAML 2.0
    SAML is by far the most common SSO protocols in use today. Your IT department will want to know that we support identity provider-initiated SSO using either Browser/Artifact or Browser/POST profiles for both SAML 1.x and SAML 2.0
  • WS-Federation
    Used almost exclusively by customers using Microsoft Active Directory and supported via Microsoft's Active Directory Federation Services (ADFS) server. We support the "Passive Requestor Profile" of this protocol The three protocols we support are widely used standards that have been through rigorous security reviews and interoperability testing with years of industry use. Many third party identity providers and application libraries are available for these standards.
Thomson Reuters does not support any protocol not listed above, including all non-standard customer-specific custom protocols.

Infrastructure Requirements

There are two options for your network infrastructure:
  1. You can use a third party identity management solution in your data center that includes support for the SAML or WS-Federation protocols. Examples include:
    • PingFederate Server
    • CA-SiteMinder
    • RSA Federated Identity Manager
    • Entrust GetAccess
    • IBM Tivoli
    • Microsoft Active Directory Federation Services server
    Each of these solutions support one or more of the standard Single Sign-On protocols. Your IT department can tell you whether they have the necessary infrastructure in place.
  2. You can use custom programming inside your internal web applications instead of deploying additional network infrastructure. Your software solution must meet all requirements of the SSO protocol being used, and generally requires in-house expertise in the granular details of the protocol.
One option that can simplify the programming is to license a third party SAML library to handle SSO protocol elements; for example the ComponentSpace .NET library for SAML 2.0 is compatible with our Single Sign-On solution if your application is .NET based.

Related content