Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As of Feb 17, all but four (4) R&S SPs have been migrated to meet the requirements of REFEDS R&S; that is, 28 of 32 R&S SPs now have a multivalued R&S entity attribute in metadata:

...

OTOH, I believe the other two (nanoHUB.org and Penn State WikiSpaces) will successfully migrate make the transition by the end of February.

Outline of Phase II

...

  1. An R&S IdP migrates to REFEDS R&S by changing its config from this:

    Code Block
    titleThe 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:

    Code Block
    titleThe 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>
  2. When an R&S IdP migrates to REFEDS R&S (as above), the entity attribute in IdP metadata will be changed from this:

    Code Block
    languageXML
    titleThe InCommon R&S Entity Attribute for IdPs
    <mdattr:EntityAttributes
        xmlns:mdattr="urn:oasis:names:tc:SAML:metadata:attribute">
      <!-- the InCommon entity attribute value for R&amp;S IdPs -->
      <saml:Attribute
          xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"
          Name="http://macedir.org/entity-category-support">
        <saml:AttributeValue>
          http://id.incommon.org/category/research-and-scholarship
        </saml:AttributeValue>
      </saml:Attribute>
    </mdattr:EntityAttributes>

    to this:

    Code Block
    titleThe REFEDS R&S Entity Attribute for IdPs
    <mdattr:EntityAttributes
        xmlns:mdattr="urn:oasis:names:tc:SAML:metadata:attribute">
      <!-- the REFEDS entity attribute value for R&amp;S IdPs -->
      <saml:Attribute
          xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"
          Name="http://macedir.org/entity-category-support">
        <saml:AttributeValue>
          http://refeds.org/category/research-and-scholarship
        </saml:AttributeValue>
      </saml:Attribute>
    </mdattr:EntityAttributes>
  3. The InCommon R&S entity attribute value is not exported to eduGAIN. That is, only Only the REFEDS R&S entity attribute value is exported to eduGAIN (whereas the InCommon R&S entity attribute value is filtered at the border of the InCommon Federation).

  4. R&S IdPs that migrate to REFEDS R&S will be automatically exported to eduGAIN once global R&S SPs have been imported into InCommon metadata.

Warning
titleOpen Question

What about new R&S IdPs? Should new R&S IdPs be allowed to declare their support for InCommon R&S only?

 

 

...

 

Once Phase II begins, the following wiki pages will need to be edited:

...