There is no need to migrate the data. These tables are for various type of tickets. Worst case when you cut over to v6.4 your users will have to login again.
-psv On Wednesday, March 30, 2022 at 9:43:58 AM UTC-5 fjan...@gmail.com wrote: > Hi, > > I need to migrate JPA service registry from Apereo CAS 5.2.2 to 6.4, > but in this last version , data structures seem to have been replaced by > just one table with flat JSON field in a column : no more relationnal > structure, or I missed something. > Has anyone here observe the same ? > If the JPA migration is not possible, does it mean I have to use JSON in > any way ? > > The best hit had met my searches till now is this page : > https://fawnoos.com/2021/01/19/cas53-service-registry-migration-to-cas63/ > But its content is pretty elliptic and I don't see where to apply the > snippet showed in it : I have an installation based on cas-overlay, > there is no java file named RegisteredServicesReportController to > override... > > In short my purpose is as follow : migration services from JPA to JSON > > Does anyone faced the same issue ? > > Thanks a lot for any clue. > > > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/133c5bb4-c6cd-4ec6-bf46-e1deaad1ffc4n%40apereo.org.