Reference Shibboleth SP Configuration Settings
Configuring the Shibboleth Service Provider to load metadata
The Shibboleth Service provider can be downloaded from the Shibboleth site for Unix or Windows platforms. The instructions that follow are for basic configuration and encourage review of the recommended readings for more detail.
Recommended reading for Service Providers:
Adding FIMS Production Aggregates to the Shibboleth Service Provider
To add the FIMS Production aggregates as trusted by your IdP after installation, edit /etc/shibboleth/shibboleth2.xml file to add the following two MetadataProvider blocks – one for the Production Domestic Aggregate and one for the Production Inter-Federation Aggregate:
<MetadataProvider type="XML" uri="https://caf-shib2ops.ca/CoreServices/caf_metadata_signed_sha256.xml" backingFilePath="CAF-metadata.xml" reloadInterval="3600"> <MetadataFilter type="Signature" certificate="md_signer.crt"/> </MetadataProvider> <MetadataProvider type="XML" uri="https://caf-shib2ops.ca/CoreServices/caf_interfed_signed.xml" backingFilePath="caf_interfed_metadata.xml" reloadInterval="3600"> <MetadataFilter type="Signature" certificate="md_signer.crt"/> </MetadataProvider>
Adding FIMS Test Aggregate to the Shibboleth IdP
To add the FIMS Test aggregate as trusted by your Service Providere, edit the /etc/shibboleth/shibboleth2.xml file to add the following MetadataProvider block:
<MetadataProvider type="XML" uri="http://caf-shib2ops.ca/CoreServices/testbed/caf_test_fed_unsigned.xml"backingFilePath="federation-metadata.xml" reloadInterval="300"> </MetadataProvider>
Note that there is no signature verification on the Test Federation.
Configuring Shibboleth Service Provider to use FIMS Central Discovery Service
Shibboleth Service Providers can be configured with a variety of different ways to assist the user to sign into the the service. This feature is called the Discovery Service step and is configured in the Session section of the Shibboleth configuration in /etc/shibboleth/Shibboleth2.xml.
Authoritative reference material for this can be found here in the ‘SSO’ section:
The default recommendation for FIMS is to use the FIMS Central Discovery Service hosted by CANARIE, which is available to all sites.
The relevant section in /etc/shibboleth/shibboleth2.xml looks like this:
<!-- Configures SSO for a default IdP. To allow for >1 IdP, remove entityID property and adjust discoveryURL to point to discovery service. (Set discoveryProtocol to "WAYF" for legacy Shibboleth WAYF support.) You can also override entityID on /Login query string, or in RequestMap/htaccess. --> <SSO entityID="https://idp.example.org/idp/shibboleth" discoveryProtocol="SAMLDS" discoveryURL=" https://caf-shib2ops.ca/DS/CAF.ds"> SAML2 SAML1 </SSO>
If you want to have users signing onto your service to be immediately directed to a specific Identity Provider, update the entityID field to the IdP of your choice.
If you want to have either a local embedded discovery service or central discovery service, update the discoveryURL accordingly. Leave discoveryProtocol as "SAMLDS".
- The CAF production discoveryURL is: https://caf-shib2ops.ca/DS/CAF.ds
- The CAF Test Federation discoveryURL is: https://ds.caftest.canarie.ca/discovery/WAYF
Recommended reading for more details on embedded discovery service can be found here: https://wiki.shibboleth.net/confluence/display/EDS10/Embedded+Discovery+Service