...
Upon completion of the steps above, after propagation of the updates (approximately one hour), testing of the new school with the IdP proxy can commence. Note, some colleges/districts will have different metadata for their prod IdP versus their pilot IdP. If so, we'll need to add their prod IdP metadata just like we did their pilot metadata in section 2.1.
Updating authsources.json
authsources.json is used by applications such as SSP and Assess to create links to other services via the SSO Proxy
...
authSource | this should be the same name used in the authsources.php file in the sso proxy configuration |
eppnSuffix | this is the scope/suffix the IDP sends with authenticating a user. This value can be found in the implementation JIRA ticket |
description | A description of the entry |
idpEntityId | The Metadata entity id of the college idp. This value can be found in the implementation JIRA ticket |
misCodes | An array of mis codes served by the college IDP. This value can be found in the implementation JIRA ticket |
authsources.json example
| Code Block |
|---|
[
{
"authSource": "idp.collegea.edu",
"eppnSuffix": "idp.collegea.edu",
"description": "College A IDP",
"idpEntityId": "https://idp.collegea.edu/idp/shibboleth",
"misCodes": [
"311",
"312",
"313"
]
},
{
"authSource": "CIMock",
"eppnSuffix": "democollege.edu",
"description": "Uni College IDP",
"idpEntityId": "https://ci-idp.ccctcportal.org:8443/idp/shibboleth",
"misCodes": [
"ZZ1"
]
}
] |
...