Deployers have multiple metadata aggregates from which to choose. This page outlines available options. Policy considerations and general configuration issues are discussed on the Metadata Consumption page. Guidance on how to configure specific Metadata Client Software is available elsewhere in this wiki.
| Warning |
|---|
InCommon DOES NOT serve metadata via TLS (HTTPS). This is intentional. TLS does not provide sufficient protection against metadata tampering. InCommon and other Research and Education federations require customers to verify the XML Digital Signature at the root of metadata documents, using a public key configured for explicit trust. Federating software that cannot:
Is not compatible with scalable multilateral SAML federation, and SHOULD NOT BE USED with InCommon or other federations. Please see the Metadata Consumption and Software Guidelines pages for more information. |
| Note |
|---|
All aggregates listed below are production-quality metadata aggregates. |
...
| Advanced Tables - Table Plus | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|
Multiple metadata aggregates allow InCommon to deploy changes to metadata more quickly, easily, and safely.
...