cas protocol behind an F5

[Niva Agmon]

Our CAS protocol users started getting errors and failing since we put our two idp nodes behind an F5 load balancer. Our setup is: two v3.2.1 idp nodes behind an F5 load balancer, using memcached for session & cas storage.

Does anyone have a similar setup that is working for them with CAS protocol and memcached behind an F5?

This is from the Cas Client server:
[Fri Aug 26 12:01:45.310071 2016] [:debug] [pid 63216] mod_auth_cas.c(1442): [client 155.247.87.98:52582] MOD_AUTH_CAS: response = <?xml version="1.0" encoding="UTF-8"?>\n<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><saml1p:Response IssueInstant="2016-08-26T16:01:45.263Z" MajorVersion="1" MinorVersion="1" ResponseID="ST-1472227304672-dq7cqqPmq8RYKYavChqbAiysK" xmlns:saml1p="urn:oasis:names:tc:SAML:1.0:protocol"><saml1p:Status><saml1p:StatusCode Value="INVALID_TICKET" xmlns="http://www.ja-sig.org/products/cas/"/><saml1p:StatusMessage>E_TICKET_EXPIRED</saml1p:StatusMessage></saml1p:Status></saml1p:Response></SOAP-ENV:Body></SOAP-ENV:Envelope>, referer: https://xxxx.temple.edu/..../

Any tips, ideas, suggestions will be highly appreciated!

Thanks,
Niva

Temple University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160902/b1785fff/attachment.html>