Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

InCommon is retiring the legacy metadata service

InCommon will retire the legacy InCommon metadata service at on Monday, March 1, 2021. All metadata clients that currently consume metadata from the legacy service must migrate to use the new metadata endpoints described in our Metadata Distribution Service documentation. Please note that this means:

  1. You must change all your InCommon-facing SAML software to consume metadata from (either MDQ or one of the aggregates)
  2. You must change all your InCommon-facing SAML software to use the new metadata signing key to verify the integrity of metadata

Instructions on these two critical changes are documented in the wiki linked above. We recommend that all InCommon participants engage with their Site Administrators and Delegated Administrators to understand the implications of this change, and to develop a plan to update all federation-facing deployments to use the new service before the old service is retired in 2021. Failure to do so will guarantee that your federation software fails to operate correctly starting with the lapse in metadata validity for the last aggregates published on the old service. You can expect this breakage to occur on Monday, March 15, 2021.


For a list of metadata client hostnames still using the legacy service, see this report, which is updated on a regular basis.

Frequently Asked Questions

Why is InCommon retiring the legacy metadata service?

With InCommon metadata approaching the 100MB mark when aggregated, it is no longer sustainable for the vast majority of deployments to continue to consume metadata from an aggregate. This would require rapidly increasing memory and CPU time to parse the metadata and verify the signature. The existing metadata signing key has been in use for over 15 years, and it's time to retire it, even though it has been carefully protected over the years. The new service is also automated, which promises faster and more frequent metadata updates in the future, and reduces staff time required to sign metadata.

Do I have to use metadata query (per-entity metadata) or can I still consume an aggregate if my metadata client isn't capable of dealing with per-entity metadata?

A) InCommon will continue to provide aggregates at the new metadata location, signed with the new key, for the foreseeable future (at least the next five years), barring an unforeseen event that forces us to retire aggregates.

How do I know if my software can use the new service?

A) If your software is currently using InCommon metadata, it is virtually guaranteed that it can use either the per-entity metadata service (Shibboleth, SimpleSAMLphp and PySAML/SATOSA are all known to work with per-entity metadata. We believe software such as CAS and ADFS will also work with per-entity metadata, to a greater or lesser extent). For clients that can't work with per-entity metadata or MDQ, you can still download aggregates.

How do I know that this new service will be stable?

The new service has been designed using modern practices and infrastructure, to offer high availability and performance. Status over the lifetime of the service can be seen at:

Why will my SAML software break two weeks after the old service is retired?

Because the metadata has a 14-day validity period, so locally cached copies of aggregates produced by the old service with the old key will continue to work for two weeks after the last batch of metadata is published.

This content is deprecated. Please see: Metadata Service

Related content

Content by Label
cqllabel in ("mdq","mdq-service","metadata-service") and space in (currentSpace(),"federation")

Get help

Can't find what you are looking for?

Button Hyperlink
titleAsk the community