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

NameURLDescription
All Entitieshttps://mdq.incommon.org/entitiesAll entities. This is akin to the legacy main aggregate available at http://md.incommon.org/InCommon/InCommon-metadata.xml
IdP Onlyhttps://mdq.incommon.org/entities/idps/allIdP-only aggregate. This is akin to the legacy IdP-only aggregate available at http://md.incommon.org/InCommon/InCommon-metadata-idp-only.xml

Get the metadata signing key

Download and place the production signing key in the credentials folder of the IdP and name it inc-md-cert-mdq.pem.


Preview MDQ

The calls listed above can also be exercised against the preview environment by pointing at https://mdq-preview.incommon.org and using the preview signing key

4 Comments

  1. Albert Wu (internet2.edu) 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 https://acme.org/idp was not correctly encoded.  It should be encoded as  https%3A%2F%2Facme.org%2Fidp in lieu of https%2F%2Facme.org%2Fidp

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