When a college is ready to integrate with the proxy the following internal and external steps must be completed:
Proxy On-boarding: Clone CIP-9 JIRA ticket template when creating a new College Proxy ticket. Make sure all sub-tasks are cloned with ticket.
Step | Who? | Description |
|---|---|---|
1 | College | College has installed or upgraded Shibboleth v3 (or equivalent supported IdP) |
2 | College | College has joined InCommon Federation Note: This is not required but is highly suggested |
3 | CCC PM | PM provides college with all required SSO & Proxy IdP documentation and checklists* |
4 | CCC PM | Creates a CIP Proxy JIRA Ticket (Clone CIP-9 with sub-tasks and revise title with college name & MIS code). PM or PO updates the Master SSO Proxy Table with JIRA ticket link. |
5 | College | College configures Pilot IdP per instructions provided** |
6 | College | College adds EntityID to metadata |
7 | College | College sends InCommon metadata to PM or Unicon |
8 | CCC PM | Attaches metadata to JIRA sub-task and assigns sub-task to Geneva P. |
9 | Unicon | Adds metadata to Pilot environment for college testing. Notifies college to test. |
10 | College | College tests Proxy in Pilot and sends feedback to PM or Unicon |
11 | Unicon | Unicon moves metadata to Production for college testing |
12 | College | College configures Production IdP per instructions provided** |
13 | College | College confirms Production Proxy works |
14 | CCC PM | Works with college to integrate with Canvas |
15 | CCC PM | Works with college to integrate with Hobsons |
16 | CCC PM | Works with college to integrate with EMSI |
17 | CCC PM | Works with college to integrate with CCCApply V3 |
*Documentation and checklists for SSO Initiative.
**Documentation and checklists for Proxy IdP Configuration based on College IdP.