[cas-user] MemcachedTicketRegistry asynchronous write to memcached

Hi there, I intermittently run into this error with my CAS 4.1.9 overlay when deployed on two CAS servers with load balancer in the front. Memcached are running on each CAS server. cas.properties has entry like this:

RE: [cas-user] Google Apps Integration Problem

Update to my earlier email: The issue (#1931) was fixed in 4.2.5-SNAPSHOT, using this version of CAS resolved the Google Apps problem. David Abney ITS Web Developer/Programmer 600 West Walnut Street Danville, Kentucky 40422 859.238.5761 [email_logo]

RE: [cas-user] Google Apps Integration Problem

Do I file an issues on the Github project, here https://github.com/apereo/cas/issues/new? Thanks, David Abney ITS Web Developer/Programmer 600 West Walnut Street Danville, Kentucky 40422 859.238.5761 [email_logo] www.centre.edu From:

RE: [cas-user] Google Apps Integration Problem

Great. I see the problem. Go ahead and file an issue please. What you are seeing below are not errors. Just DEBUG entries. Errors show up, well, as ERRORs :) And yes, you don’t have to change anything. Maintenance releases are guaranteed to be compatible.  --  Misagh From: David Abney

Re: [cas-user] Google Apps Integration Problem

Working theory: Turn your CAS logs up to DEBUG. Set a skewAllowance for googleApps to some value. Watch the logs next when you redeploy and see whether you spot the same error, or you actually see a relevant log entry about the skew allowance setting. --  Misagh From: David Abney

Re: [cas-user] Re: pac4j delegate service redirection problem

Hi, I suspect the TARGET parameter comes from the cas-client-support-saml library and you don't need it as your CAS server (v4.2) providers a /p3 endpoint so you can get user attributes without using SAML ticket validation. The pac4j-cas dependency is useless if you don't have a pac4j