Setting up IdP3 to release set of attributes only to CAS users

[Walter Forbes Hoehn (wassa)]

This is not what you are asking for exactly, but it may meet your needs.  It’s easy to apply a policy to all CAS clients within a specific domain (or set of domains) with a policy similar to this:

  <afp:AttributeFilterPolicy id=“example">
    <afp:PolicyRequirementRule xsi:type=“basic:AttributeRequesterRegex” regex=“^https://.+\.example\.edu(/.*)?$" />
    <afp:AttributeRule attributeID=“myAttr">
      <afp:PermitValueRule xsi:type="basic:ANY" />
    </afp:AttributeRule>
  </afp:AttributeFilterPolicy>

Regards,
Walter


> On Aug 13, 2015, at 11:47 AM, Jessica Coltrin <jcoltrin at pdx.edu> wrote:
> 
> To clarify a little more since there’s different ways to use CAS with Shib, we’re using the embedded CAS protocol in Shibboleth IdP3 and want to release a set of attributes to everyone that logs in using CAS protocol.
> 
> On Aug 13, 2015, at 9:42 AM, Jessica Coltrin <jcoltrin at pdx.edu> wrote:
> 
>> We’re setting up IdP3 and want to release a set of attributes to only users that login via CAS. Has anyone done this? What configuration did you use?
>> 
>> Thanks,
>> Jessica
>> 
>> -- 
>> Jessica Coltrin
>> Manager, Identity and Access Management
>> Computing Infrastructure Services
>> Office of Information Technology
>> Portland State University
>> 503-725-9599
>> jcoltrin at pdx.edu
>> www.pdx.edu/oit
>> 
> 
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net