Yes, sorry, its something that comes up when testing sometimes but rarely pops up in production. On the one hand checking it puts useless load on a backend. On the other hand, if you know what SSO and CAS does, it confuses you as to why its telling you something that shouldn't work works (it merely checks for the existence of the cookie)
We were revisiting the behavior, but I don't honestly remember where we left off on it. I'm torn since I don't like to waste resources yet I don't like to confuse people :-) On Mon, Aug 12, 2013 at 12:57 PM, Aaron Bennett <[email protected]> wrote: > From: Scott Battaglia [mailto:[email protected]] > Sent: Monday, August 12, 2013 12:47 PM > To: [email protected] > Subject: Re: [cas-user] memcache ticket registry error > > >Are you logging in to a service or hitting the login page? > > >To reduce load on backend services hitting login without a service will > not actually check a ticket. > > Good grief... no, I was just hitting the login page. That explains quite > a bit, thanks for the response. > > - Aaron > > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
