Migrating to REFEDS R&S Phase II

Outline of Phase II

Migration Process for Existing R&S IdPs

To migrate to REFEDS R&S, an IdP that supports R&S completes the following sequence of steps:

1. Review the authoritative REFEDS Research & Scholarship Entity Category specification

2. Change your IdP's attribute release policy from this:

   The configuration of an IdP that HAS NOT migrated to REFEDS R&S

   <afp:AttributeFilterPolicy id="releaseFullBundleToRandS">
   
     <afp:PolicyRequirementRule xsi:type="saml:AttributeRequesterEntityAttributeExactMatch"
         attributeName="http://macedir.org/entity-category"
         attributeValue="http://id.incommon.org/category/research-and-scholarship"/>
   
     <!-- attribute rules here -->
   
   </afp:AttributeFilterPolicy>
   

   to this:
   

   The configuration of an IdP that HAS migrated to REFEDS R&S

   <afp:AttributeFilterPolicy id="releaseFullBundleToRandS">
   
     <afp:PolicyRequirementRule xsi:type="saml:AttributeRequesterEntityAttributeExactMatch"
         attributeName="http://macedir.org/entity-category"
         attributeValue="http://refeds.org/category/research-and-scholarship"/>
   
     <!-- attribute rules here -->
   
   </afp:AttributeFilterPolicy>

   The latter configuration recognizes the REFEDS R&S entity attribute value instead of the legacy InCommon R&S entity attribute value.

3. Declare your ability to support REFEDS R&S by submitting a short form

That's all an existing R&S IdP has to do to migrate to REFEDS R&S!

When an IdP migrates to REFEDS R&S, a multivalued entity attribute is inserted into IdP metadata. Whether or not an IdP completes the migration, only the REFEDS R&S entity attribute value is exported to eduGAIN:

See the R&S Entity Metadata wiki page for details about entity attributes in metadata.

Decision Point for TAC

Two concrete options are outlined for convenience but of course a range of options is possible.

Option #1

• Existing R&S IdPs have two choices:
  1. Migrate to REFEDS R&S (as described in the previous section)
  2. Do nothing
• New R&S IdPs have two choices:
  1. Release attributes to all R&S SPs, including R&S SPs from other federations
  2. Release attributes to R&S SPs registered by InCommon only
• Messaging:
  • R&S IdPs that migrate to REFEDS R&S will be among the first IdPs exported to eduGAIN.
  • Only the REFEDS R&S entity attribute value will be exported to eduGAIN; in particular, the legacy InCommon R&S entity attribute value will not be exported to eduGAIN.
  • The legacy InCommon R&S entity attribute value will remain in InCommon metadata indefinitely.

Option #2

• Existing R&S IdPs have two choices:
  1. Migrate to REFEDS R&S (as described in the previous section)
  2. Do nothing
• New R&S IdPs have one choice:
  1. Release attributes to all R&S SPs, including R&S SPs from other federations
• Messaging:
  • R&S IdPs that migrate to REFEDS R&S will be among the first IdPs exported to eduGAIN.
  • Only the REFEDS R&S entity attribute value will be exported to eduGAIN; in particular, the legacy InCommon R&S entity attribute value will not be exported to eduGAIN.
  • The legacy InCommon R&S entity attribute value will be completely removed from metadata at the end of June 2016.