...
Once all the above steps have been completed in Pilot, you can test by using the following URLs. Once the college/district and the Proxy Project Team agree that all is working as it should with the Pilot integration, then the college/district and the Proxy Project Team can move on to Production.
Step 1 - Navigate to the Proxy Testing Web Application
To start the test your proxy integration, you will need the "Proxy Alias" that was provided by the CCC Tech Center when the Proxy Integration request was made. A Proxy Alias usually starts with "MIS" followed by the district or college level MIS Code. i.e. "MIS570"
Step 1 - Test Authentication Sources
To start the test, click on the following link:
https://sso.pilot.cccmypath.org/simplesaml/module.php/core/authenticate.php
You should see your your Proxy Alias in the list of authentication sources. If you do not see it, contact the CCC Tech Center
Step 2 - Select your Proxy Alias
You will be directed , click on the following link:
https://sso.pilot.cccmypath.org/simplesaml/module.php/core/authenticate.php?as=MISnnn
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.
If you receive an error page, either there is an issue with the IDP configuration, the MISnnn value is incorrect, or the district/college code for your Identity Provider has not yet been configured in the SSO Proxy.
Step 2 - IDP Login
The SSO Proxy will redirect you to your IDP. Log in with a known userid/password
...