CAS protocol and memcached storage in HA configuration

Scott Koranda skoranda at gmail.com
Fri Jun 19 12:34:24 EDT 2015


>     idp.session.StorageService = shibboleth.MemcachedStorageService
>     idp.cas.StorageService = shibboleth.MemcachedStorageService
> 
> 
> I apologize, but that documentation applies to a fix [1] that has not been
> released yet. The configuration in 3.1.1 requires making a change to /system/
> conf/cas-protocol-system.xml:
> 
>     <bean id="cas.ticketService" class=
> "net.shibboleth.idp.cas.ticket.SimpleTicketService"
>           c:service-ref="#{'%{idp.cas.StorageService:shibboleth.StorageService}
> '.trim()}" />
> 
> Then it ought to work as per the Wiki documentation.

I made that change and it works beautifully. Thanks.

> Thanks for your efforts to try out CAS protocol support in Shib. Your questions
> are helping work out bugs and improve documentation.

This particular deployment will have about 10 SAML2
relying parties and one CAS relying party (all external
vendors). Being able to leverage the Shibboleth IdPv3 CAS
functionality instead of having to deploy both it and the CAS
server (and then integrate them in order to have one single
place for the user authentication experience) is quite nice.

Thanks for your work adding the CAS protocol to Shib IdPv3.

Cheers,

Scott K


More information about the users mailing list