Preparation
Get the metadata for the district/college IDP and include in the CIP JIRA ticket for the district/college (found here)
If the district/college metadata is in InCommon go to InCommon section below.
...
Add the school's metadata to metadata/ccc-metadata-nextgen-unsigned.xml in the cccnext/saml-ccc Bitbucket repo to the Section marked "College IdP Metadata". It should be formatted such that long lines are wrapped.
In that same file, add a AssertionConsumerService, e.g.
<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://sso.cipilot.cccmypath.org/simplesaml/module.php/saml/sp/saml2-acs.php/MIS570" index="0"/>
to the the following Pilot and Prod IdP Proxy "SP side" SP descriptor entries. Be sure to change the "570" numeric in the example above to match the misCode of the new school or district. Each new entry should increment the index value.
Validate the metadata additions using ./validateMetadata.sh nextgen. If the validation passes, add, commit and push the change. Build automation will sign and push the updated metadata saml.cccmypath.org S3 bucket and, within one hour, downloaded to the Proxy IdP deployments.
Authsources Changes
...
aws s3 cp authsources.php s3://ccc-pilot-proxy-simplesaml-config/opt/ccc/config/
Add a new authsource entry to resources/authsources_<env>.json, where <env> is pilot and prod with the appropriate AuthSource alias, IDP entity ID, Eppn scope/suffix, description and MIS code(s) in the cccnext/saml-ccc Bitbucket repo. See example belowFor these changes to be reflected in Pilot/Prod, the Ops Jenkins “Authsources Metadata Deployment - Prod” job needs to be run.
InCommon Updates
Go to https://wwwservice1.incommoninternet2.orgedu/federationsiteadmin/siteadmin.htmllogin, click on Federation Manager sign in in the left nav and log in using Franz's InCommon creds in LastPass.
Once authenticated, change the url to https://service1.internet2.edu/siteadmin/organizations/10513/service_providers
Click on https://sso.pilot.cccmypath.org/simplesaml/module.php/saml/sp/metadata.php [ Edit ]Go about half way down the page and click on [ Edit ], service provider.
In the left hand nav, click on “SP SSO Settings”, scroll to the bottom and add the new AssertionConsumerService line that was added to the Proxy in one of the three blank fields at the bottom of the AssertionConsumerService section.
Production Onboarding
Once testing in Pilot has been verified, Metadata Change #2 (only) will need to be made for the Production environment. For this, add the same AssertionConsumerService line as done for pilot in the Prod IdP Proxy "SP side SP descriptor.
Add an entry for the new college/district in two places in the authsources.php config file in the external-config/prod/opt/ccc/config in the cccnext/idp-proxy Bitbucket repo, git add, and commit.
aws s3 cp authsources.php s3://ccc-prod-proxy-simplesaml-config/opt/ccc/config/
Add a new authsource entry to resources/authsources.json with the appropriate AuthSource alias, IDP entity ID, Eppn scope/suffix, description and MIS code(s) in the cccnext/saml-ccc Bitbucket repo. See example below.SP metadata.
Repeat that process for https://sso.cccympath.org/simplesaml/module.php/saml/sp/metadata.php service provider.
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
The file is maintained in Bitbucket in the cccnext/ccc-saml repository.
The file name in the REPO is cccnext/saml-ccc/src/resources/authsources.json
Adding a new authsources involves creating a new authSource entry in the authsources.json file with the following values
...
authSource
...
.
...
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
...