CAS Ticket storage in v3.3

[Andrew Morgan]

Are CAS Service Tickets stored differently in v3.3?

I'm testing my IDP upgrade from v3.2 to v3.3 in my DEV environment, and I 
found that tickets generated on a node running v3.3 cannot be validated on 
a different node running v3.2.  I turned up the log level and captured 
this failed validation on the v3.2 node:

2017-01-18 09:50:26,952 - DEBUG [net.shibboleth.idp.cas.flow.impl.ValidateTicketAction:92] - Attempting to validate ST-1484761826751-azH1gRsUd63kozSBauhHAujld
2017-01-18 09:50:26,952 - DEBUG [net.shibboleth.idp.cas.ticket.impl.SimpleTicketService:226] - Reading ST-1484761826751-azH1gRsUd63kozSBauhHAujld
2017-01-18 09:50:26,957 - DEBUG [net.shibboleth.idp.cas.flow.impl.ValidateTicketAction:104] - CAS ticket retrieval failed with error: {}
java.lang.IllegalArgumentException: Expected 4 fields but got 1
         at net.shibboleth.idp.cas.ticket.serialization.impl.ServiceTicketSerializer.createTicket(ServiceTicketSerializer.java:47)
2017-01-18 09:50:26,959 - INFO [Shibboleth-Audit.SSO:241] - 20170118T175026Z|||http://people.oregonstate.edu/~morgan/CAS-1.3.4/test.php|https://www.apereo.org/cas/protocol/serviceValidate||||||||ST-1484761826751-azH1gRsUd63kozSBauhHAujld|

My CAS client gets an Invalid Ticket error.

Ticket validation works fine when both nodes are v3.2 or both nodes are 
v3.3, but mixed versions do not work.

Thanks,
 	Andy