CCC Single Sign-On Technical Implementation Guide

Overview

To support the goals of the CCC SSO Federation, a proxy service has been deployed through which secure CCC web applications can centralize authentication requests for students and staff across all CCC colleges then contact the appropriate "real IdP" - such as the OpenCCC IdP - to complete the requests. The goal of this design is to simplify and accelerate system-wide technology adoption and provide uniform experiences for key users. 

The proxy serves two main functions; the first is to include the CCCID as an assertion when the college IdPs are unable to assert the CCCID from their user store.  The second is to aid in the discovery process when navigating across service providers in separate domains.Technically speaking, the proxy is designed to help colleges assert consistent SAML attributes to the various Service Providers (SP) within the CCC SSO Federation.

Use Cases

The main proxy use case is when a college is not able to send the CCCID SAML attribute for students. If the CCC Single Sign-On discovers that the student's CCCID is not present when attempting to authenticate to a particular CCC web application, it will attempt to find the CCCID associated with the IdPs unique identifier (EPPN) for the student.

If a CCCID is not found, the student will be redirected to OpenCCC to either recover or create a new OpenCCC account.  Once the account is recovered or created, the CCCID will be cross referenced to the student's EPPN so that the next time a student attempts to login to a CCC web application from their college IdP, the proxy will be find the student's CCCID and add it to the SAML attributes presented to other federation service providers.

Functions of the CCC Single Sign-On

The CCC IdP Proxy service is designed to accomplish several things:

• Provide a way to add a CCCID attribute to the SAML response to a service, even if the college is not able to provide one;

• Provide a central management point where new services can be integrated without each college needing to make any changes to its local IdP in order to access the new service;

• Instead of the SAML response from the college/district IdP going directly to the service (e.g. Canvas, Assess), it goes first to the IdP Proxy (which has it own "internal" SP).  The IdP Proxy can add attribute(s) to it if needed (e.g. CCCID), filter the attributes received down to the specific attributes needed by the particular service, and send a SAML response back to the service.

This simple diagram illustrates what this looks like: 

Before You Begin Integration with the CCC Single Sign-On

Before your college can connect to the CCC Single Sign-On, a set of minimum requirements for integration with the IdP Proxy must be met. Please review the documentation for Prerequisites for Integrating with the Single Sign-On prior to beginning the Single Sign-On integration process. The colleges should ensure that they have an SAML complaint SSO solution in place prior to the integration occurring.

Integrating with the Proxy

Once you are ready to begin, please engage with the CCC Single Sign-On team to schedule a Project Kick-off meeting. During the Proxy Project Kick-Off meeting, the following documents will be reviewed to ensure you have a good understanding of the Proxy and how to configure your IdP to integrate with it. Please be sure to discuss all existing and planned implementations with the project team to ensure all systems are connected to the Proxy during the integration process.  

• Steps to Integrate with the CCC Single Sign-On
• Attributes for the Proxy: Shibboleth
• Attributes for the Proxy: Portal Guard
• Attributes for the SSO GW: Ellucian
• Overview of Attributes for CCC SSO Federated Access
  
  

Connecting Web Applications to the Proxy

Connecting to the Proxy From Any Secure CCC Application

When your college is ready to integrate with the Proxy, a series of set up tasks must be completed regardless of which CCC application you are implementing. Please read the documents linked below and schedule your Proxy Project Kick-Off meeting with the CCC Proxy Project Team.

• Steps to Integrate with the CCC Single Sign-On
• /wiki/spaces/CSF/pages/137363670
• Proxy Integration Workflow Diagram

Connecting to the Proxy from Canvas

If your college has imiplemented the Canvas Course Management System, or is planning to implement Canvas, after you complete the initial steps to integrate with the IdP Proxy, you will need to complete an additional set of tasks to integrate Canvas with the Proxy. 

The CCC Proxy Project Team will review these steps with you when you meet for your Proxy integration kick-off meeting, Meanwhile, please review the following document and contact the Proxy Project Team if you have any questions.

Before You Begin:  Read Integrating with Canvas

Connecting to the Proxy from Hobsons/Starfish

If your college has imiplemented the Hobsons/Starfish Degree Audit System, or is planning to implement any of these education planning tools, after you complete the initial steps to integrate with the IdP Proxy, you will need to complete an additional set of tasks to integrate your Hobsons/Starfish system with the Proxy. 

The CCC Proxy Project Team will review these steps with you when you meet for your Proxy integration kick-off meeting, Meanwhile, please review the following document and contact the Proxy Project Team if you have any questions.

Before You Begin:  TBD