...
| Tip | ||
|---|---|---|
| ||
| Once you've configured your IdP to release attributes to R&S SPs 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. |
...
ACOnet Example: Configuring an IdP
Aconet provides guidance to both SPs and IdPs on its wiki pages for R&S implementation. The following is the example policy for IdPs from Aconet:
...
ACOnet provides an example attribute policy rule (and NameID overrides) for the R&S Category.
InCommon Example: Configure an IdP to Release a Fixed Subset of R&S Attributes
Configure InCommon recommends the following approach to configure Shibboleth IdP v2.3.4 (or later) to release a fixed subset of the R&S Attribute Bundle to all R&S SPs, including R&S SPs in other federations, as follows:
...
InCommon Example: Configure an IdP to Release a Dynamic Subset of R&S Attributes
Configure InCommon recommends the following approach to configure Shibboleth IdP v2.4.3 (or later) to release a dynamic subset of the R&S Attribute Bundle by filtering the actual release of attributes based on <md:RequestedAttribute> elements in SP metadata:
...