As of today, the Per-Entity Metadata Pilot has been extended for six additional months, until September 1, 2016. To find out how to participate in this effort, or to simply follow our progress in this emerging area, you are encouraged to subscribe to the metadata-support mailing list.
In June 2013, the InCommon Technical Advisory Committee convened the Metadata Distribution Working Group. The output of that Working Group included an initial set of Phase 1 Recommendations (the implementation of which is now complete) and another set of Phase 2 Recommendations (whose implementation is a work-in-progress).
One of the Working Group’s Phase 2 Recommendations is to conduct a pilot study of per-entity metadata:
RECOMMENDATION: Conduct a pilot study that explores the utility of [signed, per-entity metadata] as an alternative to metadata aggregates, and evaluate current implementations of this model to discover problems or identify new requirements.
The only SAML implementations known to support dynamic metadata query for per-entity metadata via the Metadata Query Protocol are:
If you know of other implementations that perform dynamic metadata query, please share your experiences to the metadata-support mailing list.
It is well known that Shibboleth, simpleSAMLphp, and other Metadata Client Software can automatically refresh the entire InCommon metadata aggregate. We expect that these software implementations can also refresh per-entity metadata but one of the goals of this pilot study is to demonstrate this capability. If you know of other metadata client software or SAML implementations with the ability to automatically refresh per-entity metadata, please document this fact on the metadata-support mailing list.
All questions, comments, and feedback regarding this Per-Entity Metadata Pilot should be directed to the metadata-support mailing list.
Configure your Shibboleth software deployment for dynamic metadata query!
This Per-Entity Metadata Pilot Study will last for two (2) years. Here is a rough timeline:
If the Pilot Study is successful, a production instance of a Metadata Query Server may be deployed. In any case, the beta instance of the Metadata Query Server is guaranteed to be decommissioned at the end of the Pilot Study period.
The endpoint locations of metadata served by this beta instance of the Metadata Query Server are not stable and should not be relied upon in a production setting. At the end of the Pilot Study period, this beta instance of the Metadata Query Server will be decommissioned. A production server may or may not continue in its place.
Goals and possible deliverables of this Per-Entity Metadata Pilot Study include:
If necessary, one or more conference calls will be scheduled to discuss concerns, recommendations, or topics of general interest.