This guide provides step-by-step instructions for integrating with the CCC IdP Proxy service and should be used in conjunction with the CCC IdP Proxy Integration Checklist to ensure all technical and operational requirements have been met. The process can also be visualized on the Proxy Integration Workflow diagram.
...
Once your college/district IdP is configured to release a "master bundle of attributes" to the CCC IdP Proxy, that college/district IdP won't need to be changed to be used with a new service, because all the needed changes will be made within the Proxy proxy itself. The only exception would be if an entirely new attribute was needed for a service beyond the set documented below, in which case the college/district IdP would need to be updated to release that attribute to the IdP Proxy.
...
Integrating your college/district IdP with the IdP Proxy is essentially the same steps you would follow to integrate with CCCApply, only there is a wider set of attributes that are required and/or potentially useful (optional). Basically, the idea is that the set of attributes released to the IdP Proxy is the full set of any attributes that any federated service needs. The IdP Proxy will take care of filtering that set down to what is needed for any given service. And just like with CCCApply, there is both a Pilot and Production environment for the IdP Proxy. You will integrate first with the Pilot environment, and then with Production.
...