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 | ||||||
|---|---|---|---|---|---|---|
|
Working with the metadata service
- Introducing per-entity metadata servicePer-Entity Metadata (MDQ) Service
- Information on Migrating to the MDQ Service
Production environment
Configure your software to use InCommon metadata in production.
- production-metadata
- configure-shib-idp
- configure-shib-sp
- prefetch-entity-with-shib
- configure-other-software
- production metadata signing key
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.
- preview-metadata
- configure-shib-idp-for-preview-mdq
- prefeth-entity-with-shib-in-preview-mdq
- configure-other-software
- preview-metadata-signing-key
References
Find out the latest features and changes to the MDQ Service.
- Measure MDQ performance
- Metadata Query Protocol
- Legacy metadata aggregates
- Tagging Per-Entity Metadata (for release policies, etc)
Happenings
| Info |
|---|
It's time to migrate to the MDQ ServiceThe legacy metadata service at Is your service still consuming InCommon metadata from the InCommon metadata aggregate at |
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 | ||||||||
|---|---|---|---|---|---|---|---|---|
|