Single Sign-On (SSO)
Ocelot can use a college's single sign-on (SSO) for several purposes. This document outlines the requirements and steps to implement SSO for Ocelot applications.
A few questions need to be considered before moving forward:
Does the college have separate SSO tenants for different populations (applicants, students, staff, faculty, etc)
Does the college have separate SSO tenants for production and non-production (test) applications?
Is the SSO solution SAML2 compliant?
The response to these will frame the requirements to set up SSO.
The process of setting up SSO authentication with Ocelot involves the following steps:
The college provides Ocelot with their SSO metadata, either with a URL or XML file.
Ocelot will configure our applications and return our metadata.
The college will use Ocelot metadata to configure their Identity Provider (IdP).
- When configuring your Identity Provider (IdP), Ocelot requires both the SAML Assertion and SAML Response to be signed.
If a college has separate SSO tenants for production and non-production (test) applications, then the above steps would be repeated twice (two metadata sets would be shared).
As part of the SSO authentication, Ocelot requires the following claims to be released and mapped as listed:
If any of these attributes are not available, Ocelot will work with the college to ensure we have all the required fields.