Accessing the production InCommon metadata using MDQ

The production InCommon Metadata Service is available at:

The service supports the MDQ protocol, which enables you to look up individual entity's metadata using its entity ID. To query, connect to the MDQ location with the following query string syntax:<$entityID>

where <$entityID> is the URL-encoded string of the entity ID you are searching. If you are searching for entity ID:, the web query would be:

Fully federation ready software such as Shibboleth, has built in support for the MDQ protocol. They may have configuration options to help simplify implementation. See:

Retrieving metadata as aggregates

In addition to the querying feature, the Metadata Service produces two aggregates for bulk download. They can be used in place of the legacy InCommon aggregates should you not be able to take advantage of the MDQ protocol. The IdP-only aggregate, in particular, is useful for discovery services to retrieve/list IdPs in the federations in the discovery UI.

Configure your client with an aggregate below just like you would any hosted metadata, or how you had previously configured your client to use the legacy InCommon aggregates.

You will need to configure your clients to use new signing keys issued for the environment you wish to download metadata from. The aggregates available are:

Aggregates for the Production environment

All Entities entities. This is akin to the legacy main aggregate available at
IdP Only aggregate. This is akin to the legacy IdP-only aggregate available at

Validate the signing key

Signing key: Metadata signing key for the production environment.


  1. Albert Wu ( I'm not sure of the proper way to edit this page given you're working on the space using scroll versions. I found a typo. "MDQ query" in the first subtitle should be either "metadata query" or "MDQ", not MDQ query since that's redundant.

    1. This has been updated. Thanks!

  2. Please double check that the above indicated url was not correctly encoded.  It should be encoded as in lieu of

    1. Thank you for this feedback, it has been updated.