Changes between Version 1 and Version 2 of R&Ssupport
- Timestamp:
- 07/09/12 16:42:04 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
R&Ssupport
v1 v2 1 "Configuring a Shibboleth IdP to Release Attributes to an R&S SP" 1 ==Configuring a Shibboleth IdP to Release Attributes to an R&S SP== 2 2 3 Configuring a Shibboleth IdP to Release Attributes to an R&S SP 3 4 IdP 2.3.5 and above … … 10 11 A Shibboleth IdP can be configured -- once -- to release a set of attributes to any and every R&S SP (identified by an entity attribute), not specific SPs (identified by entityID). Local IdP policy determines which attributes and values will be released. The logistics for configuring a Shibboleth IdP to do this release varies, depending on which version of the IdP a site is using. 11 12 12 IdP 2.3.5 and above 13 ==IdP 2.3.5 and above== 13 14 An IdP can choose between possible configurations, depending on its policy needs: 14 15 15 16 Always release the same set of attributes to every R&S SP. 16 17 Release only those attributes an SP requests via its metadata element. 17 Always Release the Same Set of Attributes 18 19 ==Always Release the Same Set of Attributes== 20 18 21 The following configuration requires Shibboleth IdP v2.3.5 or later, which fully supports using entity attributes in SP metadata as part of an attribute release filter policy. 19 22 20 23 Configure a new <AttributeFilterPolicy> element for R&S SPs.This example releases all of the R&S attributes; a campus should customize as appropriate (e.g., changing the attributeID values). 21 24 22 <AttributeFilterPolicy id="releaseToRandS">25 {{{<AttributeFilterPolicy id="releaseToRandS"> 23 26 <PolicyRequirementRule xsi:type="saml:AttributeRequesterEntityAttributeExactMatch" 24 27 attributeName="http://id.incommon.org/attribute/entity/category" … … 42 45 <PermitValueRule xsi:type="basic:ANY" /> 43 46 </AttributeRule> 44 </AttributeFilterPolicy> 47 </AttributeFilterPolicy>}}} 48 45 49 Release Only Those Attributes an SP Requests via Its Metadata Element 46 50 This approach relies on a plugin that is bundled with the uApprove add-on for Shibboleth. Information about uApprove is available at http://www.switch.ch/aai/support/tools/uApprove.html. It is NOT necessary for the site to run and use uApprove in order to take advantage of this plugin's capabilities. … … 56 60 The following IdP configuration implicitly releases attributes to any R&S SP. An attribute is released if and only if it is listed in SP metadata. 57 61 58 <AttributeFilterPolicy id="releaseToRandS">62 {{{<AttributeFilterPolicy id="releaseToRandS"> 59 63 <PolicyRequirementRule xsi:type="saml:AttributeRequesterEntityAttributeExactMatch" 60 64 attributeName="http://id.incommon.org/attribute/entity/category" … … 78 82 <PermitValueRule xsi:type="ua:AttributeInMetadata" onlyIfRequired="false"/> 79 83 </AttributeRule> 80 </AttributeFilterPolicy> 81 IdP Previous to v2.3.5 84 </AttributeFilterPolicy>}}} 85 86 ==IdP Previous to v2.3.5== 82 87 These releases do not correctly support using entity attributes in SP metadata as part of an attribute release filter policy. For IdPs prior to v2.3.5, InCommon provides a tool that can be run on a regular basis to convert InCommon metadata into an explicit <AttributeFilterPolicy> element for R&S SPs. 83 88 84 Further Policy Controls 89 ==Further Policy Controls== 85 90 If a campus determines that it wants to block release of attributes for certain community members (e.g., students who have opted out under FERPA), IdP operators could create an additional attribute release policy to enforce this decision. An example is available on the Shibboleth wiki. IdP plugins, such as uApprove, that provide end-user control over attribute release may also be useful to satisfy additional controls.
