I recently went thru a similar upgrade from 3.5 to 6.3.x We did not update any of our cas client jars (using 3.6) and all appeared to still work. Even our shibboleth idp 4.x was still working. Only problem we had was where some app owners where creating their own cas client using python and flask ... the ticket validation response was different enough to break those apps. I'd image if a standard cas client library was used they would not have had a problem.
-psv On Saturday, January 29, 2022 at 1:43:48 PM UTC-6 [email protected] wrote: > Hi, > > In order to have an "authoritative" answer to this question I will be > asked soon : can old CAS clients (like PhpCAS) used with an old version > (unmaintened but still used webapps created when our CAS 3.5 appeared) work > with the latest versions ? > > Is everything backward compatible as long as the setup is similar, and the > same protocol versions are used ? > > After reading posts like this one : > https://fawnoos.com/2017/06/23/cas-protocol-compatibility/ it seems some > adjustments are needed here and there. > > So far, all our stuff is working fine with a CAS 3.5 instance, and I plan > to deploy a 6.4 to replace it. > > Regards > > ------------------------------ > FreeMail powered by mail.fr -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/729aa574-f755-42c1-9c8c-2aa660760b3dn%40apereo.org.
