Windows SP 2.6.0

[Rory Larson]

Hello,

We are on 3.2.1, and are interested in releasing a non-standard attribute to a particular service provider via CAS.  We are puzzled though on how the connection is made between the SP included within a regex in the CAS service registry in {shibhome}/conf/cas-protocol.xml, and the SP for whom the attribute is released in attribute-filter.xml.  Do we simply add the SP with the appropriate attribute release in attribute-filter.xml and expect that CAS will release it to that SP accordingly, or more setup required?  For example:

SP = studentapp.my-u.edu

In cas-protocol.xml:

                <bean class="net.shibboleth.idp.cas.service.ServiceDefinition"
                      c:regex="https?://([A-Za-z0-9_-]+\.)*my-u\.edu(:\d+)?/.*"
                      p:group="My-U Services"
                      p:authorizedToProxy="false"
                      p:singleLogoutParticipant="true" />

    already allows https://studentapp.my-u.edu to be a CAS client.

In attribute-filter.xml, we add:

	<AttributeFilterPolicy id="studentapp-authservice">
	   <PolicyRequirementRule xsi:type="basic:AttributeRequesterString" 					                  value="https://studentapp.my-u.edu/shibboleth" />
	
	    <AttributeRule attributeID="campusID">
	      <PermitValueRule xsi:type="basic:ANY" />
	    </AttributeRule>

	  </AttributeFilterPolicy>

Is this all we have to do?  (Other *.my-u.edu CAS clients should not have access to campusID.)

Thanks,
Rory