Page History

Phase 1 Implementation Plan

This document is a DRAFT plan to implement the Phase 1 Recommendations of the Metadata Distribution WG.

...

1. On December 18, 2013, InCommon Operations will deploy two new metadata aggregates at the following permanent HTTP locations:
   • http://md.incommon.org/InCommon/InCommon-metadata.xml (production metadata)
   • http://md.incommon.org/InCommon/InCommon-metadata-fallback.xml (fallback metadata)
2. Both metadata aggregates will be signed using a new self-signed signing certificate set to expire on December 18, 2037.
   • Although the signing certificate is new, the signing key is not.
3. Both metadata aggregates will be signed with the same key but the fallback metadata aggregate will use a different digest algorithm.
   • Both the The production metadata aggregate and the preview metadata aggregate will be signed using a SHA-2 digest algorithm (specifically, SHA-256).
   • Initially, the fallback metadata aggregate will be signed using the SHA-1 digest algorithm (which is what we use now).
4. All deployments shall migrate to one of the new metadata aggregates ASAP but no later than March 29, 2014.
   • The current metadata aggregate will be replaced with a redirect to the fallback metadata aggregate on March 29, 2014.
   • If your metadata process can verify an XML signature that uses the SHA-256 digest algorithm, migrate to the production metadata aggregate or the preview metadata aggregate.
   • If your metadata process can not verify an XML signature that uses the SHA-256 digest algorithm, migrate to the fallback metadata aggregate.
5. All deployments shall be able to verify an XML signature that uses a SHA-256 digest algorithm by June 30, 2014.
   • On June 30, the fallback metadata aggregate will be synced with the production metadata aggregate (i.e., all aggregates will be signed using the SHA-256 digest algorithm).
   • After June 30, all metadata aggregates published by the InCommon Federation will be signed using the SHA-256 digest algorithm.

See the Phase 1 Implementation Plan FAQ for more information.

...

Policy

It is strongly recommended that InCommon SPs and IdPs refresh and verify metadata at least daily. The security implications of metadata refresh are discussed on the Metadata Consumption wiki page:

...

1. The InCommon metadata signing certificate expires on May 2, 2014.
   • If we don't issue a new metadata signing certificate by May 2, 2014, an expired signing certificate will be bound to the XML signature in metadata.
2. The InCommon metadata signing certificate is signed by a legacy CA whose certificate expires on March 29, 2014.
   • If we don't issue a new metadata signing certificate by March 29, 2014, an expired CA certificate will be bound to the XML signature in metadata.
   • The CA certificate adds nothing to the security of metadata, so its presence (expired or not) only serves to confuse consumers.
3. The XML signature on InCommon metadata uses the deprecated (and soon-to-be disallowed) SHA-1 digest algorithm.
   • NIST deprecated the use of SHA-1 in conjunction with digital signatures on January 1, 2011.
   • NIST disallows the use of SHA-1 in conjunction with digital signatures after January 1, 2014.
   • See: NIST SP 800-57 Part 1, Revision 3 (July 2012), Tables 3 and 4
4. Multiple, heterogeneous services currently run on vhost wayf.incommonfederation.org, namely, Metadata Services and the Discovery Service. To provide better quality of service, these services need to be segregated onto their own vhosts (md.incommon.org and ds.incommon.org, resp.). This will allow us to fine-tune each service according to its requirements.
   • Note: The InCommon Federated Error Handling Service is already running on ds.incommon.org.
5. Multiple metadata aggregates will allow us to deploy changes to InCommon metadata more quickly and safely. Metadata consumers will have options depending on the requirements of each their deployment.

Actions

InCommon Operations will take the following actions:

...