...
| Note |
|---|
| If your SP deployment depends on the R&S entity attribute in IdP metadata, please read on. Otherwise there is nothing further you need to do. |
An SP configuration that deployment that depends on the R&S entity attribute in IdP metadata almost certainly recognizes the legacy incommon.org R&S entity attribute value:
...
since IdPs that support global R&S will necessarily carry the latter in their metadata. Indeed, R&S IdPs from other federations will carry the refeds.org R&S tag exclusively.Today an InCommon IdP that supports global R&S (i.e., releases attributes to ALL R&S SPs) has a multivalued R&S entity attribute in its metadata. Eventually this multivalued R&S entity attribute will be removed.
| Warning | ||
|---|---|---|
| ||
| An If an SP configuration depends on the R&S entity attribute in IdP metadata, it SHOULD recognize both R&S tags independently but it MUST NOT rely on the multivalued entity attribute in any way. Eventually every R&S IdP will have a single-valued R&S entity attribute in metadata. A timeline for doing so has not yet been determined. |
...
| carry either the incommon.org R&S tag |
...
| or the refeds.org R&S tag |
...
| , but |
...
| not both. An SP that depends on the |
...
| R&S entity attribute in IdP metadata must take this fact into account. |
For example, an SP that filters metadata to restrict its discovery interface to R&S IdPs only might do the following...