The Incommon Federation wiki has moved.

Please visit the new InCommon Federation Library wiki for updated content. Remember to update your bookmarks.

Click in the link above if you are not automatically redirected in 15 seconds.



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

This is a roadmap for operationalizing eduGAIN participation in the InCommon Federation.

Operational Timeline

The following timeline for operationalizing eduGAIN was obtained by working around the milestone date February 10, 2016, the date by which all non-technical requirements will have been met.

Contents:

 

A Global Metadata Aggregator that imports eduGAIN metadata as outlined in this document has been developed and deployed by InCommon Operations. Using this new infrastructure, a snapshot of InCommon metadata was taken on January 15, 2016.

Milestones

Phase 0 [DONE] Introduce the MD-RPI schema

Introduce the MD-RPI schema into production metadata.

  • Introduce the <mdrpi:RegistrationInfo> element into production metadata
  • Introduce the registered-by-incommon entity attribute into production metadata
  • Introduce the <mdrpi:PublicationInfo> element into production metadata
    • Align with the <mdrpi:PublicationInfo> element in the export aggregate

For more info: Registered By InCommon Category

Phase 1 [DONE] Deploy user interfaces in the FM

There are 1037 global SP entities in eduGAIN metadata (as of January 15, 2016)

Deploy user interfaces in the Federation Manager. Perform the following operations:

  1. Deploy an updated user interface for requested attributes in the Federation Manager
    1. Deprecate SAML1-format <md:RequestedAttribute> elements in SP metadata
    2. Support the isRequired XML attribute in SP metadata
  2. Deploy a user interface for IdPs in the Federation Manager
    1. Give Site Administrators the ability to self-assert membership in the Hide From Discovery Category
  3. Deploy initial user interfaces for IdPs and SPs in the Federation Manager
    1. Give Site Administrators the ability to opt out of default export of IdP metadata
    2. Give Site Administrators the ability to explicitly opt into the export of SP metadata

For more info: FM Change Log

Phase 2 [DONE] Import eduGAIN metadata into the preview aggregate

There are 1521 global IdP entities in eduGAIN metadata (as of January 15, 2016)

Import eduGAIN metadata into the preview aggregate. Perform the following operation:

  1. Import global metadata into the preview aggregate
    1. Advise deployers to point their pre-production systems at the preview aggregate

Post-Phase 2 Metrics

Upon completion of Phase 2 (on January 15, 2016), the InCommon preview aggregate was over 32MB in size, with 1934 IdPs and 3635 SPs.

Phase 3 [February 15, 2016] Begin production integration with eduGAIN

Sync the main production aggregate with the preview aggregate and begin exporting metadata at scale to eduGAIN. Perform the following operations in order:

  1. Deploy final user interfaces for IdPs and SPs in the Federation Manager
    1. Continue to give Site Administrators the ability to opt out of default export of IdP metadata
    2. Continue to give Site Administrators the ability to explicitly opt into the export of SP metadata
  2. Import global metadata into the main production aggregate
    1. Sync the main production aggregate with the preview aggregate
    2. Maintain the fallback aggregate for a minimum of one month
  3. Export InCommon metadata to eduGAIN
    1. Export all IdP metadata by default, except those IdPs that have explicitly opted out
    2. Export SP metadata on demand, for those SPs that have explicitly opted in

Phase 4 [March 15, 2016] Complete production integration with eduGAIN

Sync all metadata aggregates in the pipeline.

  1. Import global metadata into the fallback aggregate
    1. Sync the fallback aggregate with the main production aggregate.

 

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels