Error during deserialization with Memcached TicketRegistry and RememberMe
Description
Environment
Attachments
Activity
Jérôme LELEUJanuary 13, 2014 at 3:21 PM
Fixed in 4.0
Jérôme LELEUJanuary 13, 2014 at 3:21 PM
OK. Thanks for your understanding...
Vincent HURTEVENTJanuary 13, 2014 at 3:11 PM
I understand. It works with the default serializer. If it's not a performance issue, last stable 3.5.2 with these settings are fine for me.
I'll go with 4.0 when it's been released.
Jérôme LELEUJanuary 13, 2014 at 3:05 PM
I just made the test and yes, I've got the same problem with 3.5.2: https://github.com/leleuj/cas-overlay-3.5.x/commit/37116e61f4fb20bf146f6980b6486edde77fb842.
We are so close from the 4.0 release that I'm not sure we'll have a 3.5.3 though...
Jérôme LELEUJanuary 9, 2014 at 4:44 PM
Sound logical. There must be some trouble with the Kryo serializer (https://github.com/Jasig/cas/tree/3.5.x/cas-server-integration-memcached/src/main/java/org/jasig/cas/ticket/registry/support/kryo/serial).
I would try to update the test: https://github.com/Jasig/cas/blob/3.5.x/cas-server-integration-memcached/src/test/java/org/jasig/cas/ticket/registry/support/kryo/KryoTranscoderTests.java to add some TGT serialization like in 4.0 with a boolean value as an authentication attribute: https://github.com/Jasig/cas/blob/master/cas-server-integration-memcached/src/test/java/org/jasig/cas/ticket/registry/support/kryo/KryoTranscoderTests.java.
Details
Assignee
Jérôme LELEUJérôme LELEUReporter
Vincent HURTEVENTVincent HURTEVENTComponents
Affects versions
Priority
Major
Details
Details
Assignee
Reporter
Components
Affects versions
Priority
Major
When I log in through CAS, it goes well, but when the app ask for ST validation, CAS server ends with an error regarding deserialization of the TGT pulled from the memcache TicketRegistry.
It seems that the deserialization process doesn't expect the boolean value which sets the rememberMe flag.
Logs : https://gist.github.com/vhurteve/8284303