...
Once you've configured your IdP to release attributes to all R&S SPs (both present and future) as described below, you should optimize your IdP configuration files by removing all references to the entity IDs of individual R&S SPs. (That is, in fact, the whole point of using entity attributes to configure attribute release policy.)
| Warning | ||
|---|---|---|
| ||
All configuration examples below recognize the REFEDS R&S entity attribute value: http://refeds.org/category/research-and-scholarship An IdP that supports REFEDS R&S (by recognizing the REFEDS R&S entity attribute value) implicitly releases attributes to all R&S SPs, including R&S SPs in other federations. IdPs that are unwilling and/or unable to implement such a policy should consider releasing attributes to R&S SPs registered By InCommonby InCommon (by recognizing the REFEDS R&S entity attribute in part). |
Contents:
| Table of Contents | ||
|---|---|---|
|
...
Software Requirements
To release attributes to all R&S SPs with a single configuration, an IdP leverages entity attributes (instead of entity IDs). Thus the configuration steps documented here require Shibboleth IdP v2.3.4 or later, which fully supports using entity attributes in SP metadata as part of an attribute release filter policy.
...