CAS Protocol Service Registry (Shib 3.3)

Dan Malone dmalone at calpoly.edu
Tue Jan 2 15:38:41 EST 2018


We are looking for a way to simplify the configuration of our CAS services.
In our current CAS usage, we are not doing any additional attribute release, only username.

 From what we can tell, to enable a CAS client, at a minimum we need to do two things:

 1. add the service URL in the cas.serviceRegistry bean in cas-protocol.xml
 2. release the username attribute in attribute-filter.xml

To make it easier to add new services, we would like to be able to add the service in once place.

For option A, we add a very permissive wildcard to cas-protocol.xml and control services using attribute-filter.xml. We got this to work, but when you have an unauthorized service, a ticket is granted and the failure is not noticed until the verification step. Neither the user or the service knows why because the ticket was issued.

For option B, we would like to use cas-protocol.xml to limit the services and in attribute-filter.xml, release username to all CAS services. This provides the user friendly message "...application you have accessed is not registered..." similar to pre-shib CAS. However, we can not use the very permissive wildcard in attribute-filter.xml, because this would also release via SAML to all entities in, for example, the InCommon metadata, and our campus is not ready to release to R&S, much less the whole aggregate. (Yes, we're working on the R&S release)

So, here's my question:

How do we release an attribute to all services defined in the cas.serviceRegistry bean list?

Thanks,
Dan

-- 
Dan Malone
Lead Identity Management Architect
Information Technology Services
California Polytechnic State University
San Luis Obispo, California

Direct 805-756-6326
dmalone at calpoly.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180102/9fbe23e0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4207 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20180102/9fbe23e0/attachment.p7s>


More information about the users mailing list