Page History

...

Every R&S SP has a multivalued R&S entity attribute in metadata so that R&S IdPs can migrate to global R&S at any time without loss of interoperability. Eventually the legacy incommon.org R&S tag in SP metadata will be removed.

Why is it necessary to remove the legacy incommon.org R&S tag from SP metadata?

...

The Research & Scholarship category is now an international standard. The legacy incommon.org R&S tag is only relevant inside the InCommon Federation. In order to interoperate with international partners, the legacy incommon.org R&S tag must be replaced with the new refeds.org R&S entity attribute value, which is the only R&S entity attribute value recognized by R&E federations worldwide.

 

When will the legacy incommon.org R&S tag be removed from SP metadata?

...

We have no definite plans to remove the legacy incommon.org R&S tag from SP metadata. We will monitor the progress of the Research & Scholarship category in the InCommon Federation and make a determination at a later time. In the meantime, it is RECOMMENDED that all IdPs remove all references to the legacy incommon.org R&S tag from their configurations.

...

Under no circumstances will an IdP receive a multivalued R&S entity attribute. An IdP receives the refeds.org R&S tag if and only if it releases attributes to all R&S SPs globally. If, OTOH, an IdP releases attributes to R&S SPs registered by InCommon only, it will receive the incommon.org R&S tag. 

When will the incommon.org R&S tag be removed from IdP metadata?

As long as there are IdPs that want to restrict attribute release to R&S SPs registered by InCommon, the legacy incommon.org R&S tag will remain in IdP metadata. Be aware, however, that the incommon.org R&S tag will not be exported outside the InCommon Federation. If and when your IdP metadata is exported to eduGAIN, it will not contain an R&S entity attribute at all. From a global perspective, you do not support R&S unless you recognize the refeds.org R&S entity attribute value. 

...