CAS protocol and memcached storage in HA configuration

[Marvin Addison]

>
> Specifically I have set
>
> 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.

When I run memcached with the -vv option I see the node the
> browser is hitting output this (minus the actual binary data):
>

I believe that output is for storage/retrieval of IdP session data in
memcached, not CAS tickets.


> Should the node the CAS client is hitting have been able to
> find the service ticket, or am I misunderstanding the
> memcached storage implementation?
>

It will work if you make the change above that I suggested. I'm running the
exact same configuration in our dev environment, and I'm seeing browser
requests go to one node and CAS client requests go to the other, and it
works splendidly.

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

M <users-unsubscribe at shibboleth.net>

[1] https://issues.shibboleth.net/jira/browse/IDP-640
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150619/bafebbd5/attachment.html>