Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

StepWho?DescriptionDocument / Link
1CollegeCollege has installed or upgraded Shibboleth v3 (or equivalent supported IdP)Upgrade Shibboleth V2 to V3
2CollegeCollege takes steps to join InCommon Federation (Note:Not required at time of Proxy integration, but is highly recommended.)Joining InCommon Federation
3CCCCCC schedules kick-off meeting with college and ensures they understand all required Proxy integration documentation
4CCCCreates a CIP Proxy JIRA Ticket and begins project management tasks 
5College

College completes Steps A -F for Pilot & Production on Steps to Integrate with the CCC SSO Proxy 

Please contact Proxy Team if you have any questions
6CollegeCollege adds EntityID to metadataSee Steps to Integrate with the SSO Proxy
7CollegeCollege sends configured metadata to Proxy Project Team for upload to the Pilot proxy instanceProxy Team: Patty Donohue, CCC
Geneva Paliwodzinski, Unicon 
8CCCAttaches metadata to JIRA sub-task and assigns sub-task to Geneva P. 
9UniconUploads metadata to Pilot environment for college testing. Notifies college to test. 
10CollegeCollege tests Proxy in Pilot and sends feedback to PM or UniconSend feedback to Proxy Project Team
11UniconUnicon moves metadata to Production for college testingProxy Team will contact College when ready to test
13CollegeCollege confirms Production Proxy worksSend feedback to Proxy Project Team
14CCCIf College has implemented Canvas: Complete steps to integrate Canvas with SSO Proxy See Integrate with Canvas
15CCCIf College has implemented Hobsons: Contact SSO Proxy Project Team for proxy integration steps.Contact Proxy Project Team
16CCCIf College is implementing EMSI Career Coach - No additional steps are required. 

 

For Internal Use Only

Note

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.