...
STEP 4: Configure your Identity Provider to consume the metadata for the CCC SSO Proxy
...
| Info | ||
|---|---|---|
| ||
f you are running a Shibboleth IdP v3 server, with the configuration changes made by Unicon |
...
, or if your Identity Provider is configured to consume metadata from InCommon, your IDP will already have access to the SSO Proxy SAML metadata and you can skip this step. |
The new IdP v3 config that has been put in place includes consuming a CCC system-wide, centrally managed digitally-signed metadata file from a URL (with verification of the signature for security.) The IdP automatically checks for updates for that file, and reloads it if such have been made.
...
Just as with the CCCApply service, you will start with Pilot, and once that is working and you are given the "go-ahead", then download the metadata for Production. Note: you need to replace the 'nnn' at the end of each URL with the MIS code that applies to your district (if a district-wide IdP) or to the college (if a single college IdP). The CCC IdP Proxy Service Team will confirm with you what that code will be for your IdP.
| Pilot | https://sso.pilot.cccmypath.org/simplesaml/module.php/saml/sp/metadata.php/MISnnn |
| Production | https://sso.cccmypath.org/simplesaml/module.php/saml/sp/metadata.php |
...