IAM in Service Catalog
This page describes Shibboleth Service Provider (SP) configuration necessary to download the UW Identity Provider (IdP) local metadata file and, optionally, verify the digital signature.
The UW is part of the InCommon federation and publishes its IdP metadata in the InCommon metadata aggregate (http://md.incommon.org/InCommon/InCommon-metadata-idp-only.xml). However, the InCommon metadata aggregate has grown large enough to cause problems for SPs when they attempt to download the file and verify the digital signature. Symptoms include high memory utilization, very slow restarts, and occasional failures to restart the shibd process.
To mitigate these issues, InCommon now provides a Per-Entity Metadata Service that queries for the specified IdP and caches frequently called IdPs. This service, also know as MDQ (based on the IETF "Metadata Query" protocol), is available at https://mdq.incommon.org. Please see Configure a Shibboleth SP to use the InCommon Per-Entity Metadata Distribution Service for more information about this service. Note: some Service Providers are unable to consume a multi-entity metadata aggregate mandating the use of UW IdP metadata.
For Service Providers who wish to consume a small, static metadata file, the UW IdP publishes a local copy of its metadata and digitally signs the file. The sections below describe the SP configuration necessary to download the local metadata file and (optionally) verify the digital signature. If the local IdP metadata is downloaded from https://idp.u.washington.edu/metadata/idp-metadata.xml, the HTTPS protocol provides integrity and signature verification is optional (but recommended). If the IdP metadata is obtained from other sources, the digital signature should be verified. If signature verification will be used, the SP must keep a copy of the IdPs signing certificate in its configuration.
SPs that are federated to accept users from other (non-UW) InCommon IdPs should not use this configuration. They will require the InCommon Per-Entity Metadata Service located at (https://mdq.incommon.org/). The configuration described below is intended for SPs that rely only on the UW IdP. For more information see Configure a Shibboleth SP to use the InCommon Per-Entity Metadata Distribution Service.
shibboleth2.xmlfile for editing.
Add the following
MetadataFilter element says that the signature on
idp-metadata.xml should be verified using the
If you have configured a
MetadataProvider for the InCommon metadata aggregate, you should comment it out or delete it.
shibboleth2.xmlfile. Name it something like
MetadataProviderlocations and to download any updates. Shibboleth will also verify the digital signatures on any metadata where it is configured to do so.
Look for messages like the following (numbering added for clarity, these are not present in the log file):