Page History

...

The R&S Migration Process

To support the R&S category, either globally or locally, the operator of an existing R&S IdP follows this simple 3-step process:

1. Review the authoritative REFEDS Research & Scholarship Entity Category specification
   
   1. The requirements for an R&S SP have changed slightly (a gap analysis has been prepared for your convenience)
   2. The requirements for an R&S IdP have not changed
      
2. Configure your IdP to release attributes to R&S SPs, either globally or locally (see subsequent sections)
3. Declare your IdP's ability to support R&S by submitting a short form
   

Use of the Legacy R&S Tag

If you support R&S today, your IdP is likely configured with a policy rule that releases attributes to R&S SPs tagged with the legacy incommon.org R&S entity attribute value, something like this:

...

Thus all R&S IdPs should be reconfigured to not rely on the legacy incommon.org R&S tag. Although we have no immediate plans to remove that tag from SP metadata, we reserve the right to do so in the future. We will of course let you know in advance if and when this happens but in the meantime we ask that you remove the legacy incommon.org R&S tag from your IdP configuration. Doing so now prevents you from having to do so later on.

Supporting the R&S Category

To support the R&S category, either globally or locally, the operator of an existing R&S IdP follows this simple 3-step process:

1. Review the authoritative REFEDS Research & Scholarship Entity Category specification
   
   1. The requirements for an R&S SP have changed slightly (a gap analysis has been prepared for your convenience)
   2. The requirements for an R&S IdP have not changed
      
2. Configure your IdP to release attributes to R&S SPs, either globally or locally (see subsequent sections)
3. Declare your IdP's ability to support R&S by submitting a short form
   

...

.

Releasing Attributes to All R&S SPs

...