Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space mdqedit and version 1.2

The InCommon Metadata Distribution Service (MDQ Service) facilitates secure and trusted exchange of critical organizational identity, service location/capability, and contact information among identity providers and service providers.

Find and retrieve metadata for identity providers and service providers in InCommon and R&E federations around the world using the InCommon Metadata Distribution Service.


Livesearch
spaceKeyMDQ
sizelarge
placeholderSearch Documentation


Working with the metadata service

Production environment

Configure your software to use InCommon metadata in production.

Preview environment

The "preview" MDQ Service environment allows you to validate your service against upcoming changes to the MDQ Service. 

Preview environment status: the preview environment current mirrors the production environment.

References

Find out the latest features and changes to the MDQ Service.

Other Federation topics 

Button Hyperlink
iconsearch
titleVisit the InCommon Federation Library wiki
typeprimary
urlfederation:InCommon Federation Library

Happenings

Info

It's time to migrate to the MDQ Service

The legacy metadata service at md.incommon.org is retiring in March 2021.

Is your service still consuming InCommon metadata from the InCommon metadata aggregate at md.incommon.org? If so, it's time to migrate to the new InCommon Metadata Service (MDQ Service). See Migrating to the MDQ Service to find out more. 

Keeping everyone safe - we are moving legacy metadata signing online.

To comply with the State of Michigan's limited shelter-in-place/stay-at-home executive order, we are replacing our in-person metadata signing process used to sign the legacy metadata aggregate with a secure cloud-based signing process,  originally developed for MDQ. To learn more, read on.

Additional Resources


Want to see how adopting the MDQ metadata service affects your system's performance?

Here is an in-use memory graph at the moment a university switched to using MDQ in its production IDP servers:


Great results from a Service Provider:
"We were able to switch to using MDQ. The service restarts in 5 seconds now versus 15 minutes."

Service Level Objectives

The production endpoints of this service are designed to meet the following requirements on a best-effort basis:

  • 99.9% availability
  • <= 200ms per request from clients on the Internet2 network
  • Metadata validity window of no less than 5 business days (metadata is valid for 14 days, but may be signed infrequently over extended holiday periods)
  • You can see the status of InCommon services on our status dashboard

It's worth noting that since launch, both the technology preview and production environments have had 100% availability.

Other Federation topics 

Button Hyperlink
iconsearch
titleVisit the InCommon Federation Library wiki
typeprimary
urlfederation:InCommon Federation Library