Introduction:

This document outlines Webassessor Single-Sign-On (SSO) integration using Security Assertion Markup Language (SAML) instead of OAuth2. Both approaches are offered by Kryterion, Inc. to its clients.

Before implementing SAML into Webassessor it is important to understand that SAML, unlike OAuth2, has just two entities,

• Identity Provider (IdP) – Always the Client.
• Service Provider (SP) – Always Webassessor.

Purpose:

The following high-level overview of Kryterion’s standard Webassessor SSO integration using SAML summarizes the applicable implementation integration points and boundaries. 

References:

[SAML]: The SAML specification documentation is available at: http://saml.xml.org/saml-specifications
For your reference, here is the link to the integration document for an OAuth2 implementation.

Pre-requisites:

• Since the SSO follows SAML specification, in order for a client to be able to effectively integrate with Webassessor for SSO, the client should either have an in-house IdP server or should be able to use a 3rd party IdP like Okta, Salesforce, etc. 
• Client should be created in the Webassessor system as an entity and region with a brand since they are part of communication during SSO calls.

Integration Points and Flows