Mohamed,

Version 6 is in maintenance mode, 
https://apereo.github.io/cas/developer/Maintenance-Policy.html#eol-schedule
You can move to version 7 without going through 6 first.

Ray

On Sat, 2024-01-20 at 08:38 +0100, Mohamed Amdouni wrote:
Notice: This message was sent from outside the University of Victoria email 
system. Please be cautious with links and sensitive information.

Hello,

For me it is a migration from 5.x to 6.x.

I think that enabling export services needs also some spring management 
properties to be added ( in addition to cas if it exists )


Best regards

Le sam. 20 janv. 2024 à 06:16, Ray Bon <r...@uvic.ca<mailto:r...@uvic.ca>> a 
écrit :
To get a list of all properties (and some defunct ones) run:

./gradlew exportConfigMetadata

During startup, cas logs properties that are deprecated and prints out the 
current property key.

You are upgrading to 7 and not 6, right?

Ray

On Fri, 2024-01-19 at 11:23 -0800, atilling wrote:
Notice: This message was sent from outside the University of Victoria email 
system. Please be cautious with links and sensitive information.

Dave Steiner,

Could you share your cas.properties file or a snippet of it so I can see how 
you enabled /status/services/export ? The CAS 5 documentation has been removed 
from GIT so I'm not finding information on how to enable.

On Tuesday, June 28, 2022 at 5:14:27 PM UTC-4 Dave Steiner wrote:
We are currently upgrading from v5 to v6 and use JPA like you are.  What we are 
doing is to use the CAS5 endpoint  /status/services/export to get a zip file of 
all our Service entries (~1000-1500).  We then need to make a minor change to 
those and will be using the CAS6 endpoint  /actuator/registeredServices/import 
to import each json file individually (we tried giving it a new zip file but it 
was duplicating entries for some reason).  I'm currently playing with this on 
Dev and will hopefully do this on Test in a few weeks.

-ds

On Wednesday, June 15, 2022 at 12:43:23 PM UTC-4 Trevor Fong wrote:
Thanks a lot for your reply Francois.

Dammit - that sucks that we both had such a poor experience!
I fear you might be right and I'll have to abandon the 300+ rules we've built 
up over the years due to inadequate support and documentation; it's not like 
they discontinued support for JPA - they just didn't provide any support at all 
for migration, which feels worse!  It's like saying "Sure you can do it, see 
all the cool things you can do" and not say how to do it.
I'll give myself to the end of the week and "cut bait" if I can't find a way 
out.  I'll reply if I should find anything of use.

Thanks again,
Trev

On Wed, 15 Jun 2022 at 08:11, fjannin4 <fjan...@gmail.com> wrote:

Hi Trev

Alas I didn't found anything to simply convert structured data from JPA to 
JSON... It was too tedious and time consuming and I gave up... None of cues and 
hints was working.

The whole online documentation of CAS 5.x has been removed (i have never seen 
so many Google results issueing 404 errors... dunno why they don't remove links 
?) , to enforce difficulty to find relevant informations, and I mess up working 
with partial remains in webarchives.

Instead I am going to replace my fine tuned granularity of service descriptions 
with one wildcard by domains name of internal applications, in JSON format, the 
only one that really has support from CAS Team and documented.

Doing this therefore, I will lost all level of details for each service : 
descriptions, logo and contacts, thas was before used in CAS and CAS management 
application...

High price to paid, just for CAS developpers team's taste to follow the fahsion 
for JSON and unilateral deprec    tion for JPA ...

So, to keep your CAS installation working is a question of chance : if you bet 
on the good techno that wil survive to annual elegation, you won... We bet on 
JPA and lost...

Good luck !
Regards

Le 10/06/2022 à 19:45, Trevor Fong a écrit :
Hi Francois,

Just wondering if you were able to resolve your situation and if so, how?  I'm 
also facing a similar thing.

Thanks a lot,
Trev

On Thursday, March 31, 2022 at 10:54:41 AM utc-7fjan...@gmail.com wrote:

Thank you for the response.

We actually use CAS Management application, and I will follow your suggestion.

We have a bunch of services  to migrate : 140+, with their own contacts, 
policies and release attriibute settings.

I have tried the actuator end point /services from CAS Server , wich export all 
services in one file, but  JSON format seems different from the import format 
used in CAS 6.4.

i will try the management application way, with hopefully more success...

Best regards

Francois

Le 31/03/2022 à 17:35, 'Richard Frovarp' via CAS Community a écrit :
The tables in the post are for the service registry. If you don't migrate 
those, you will have to reconfigure from scratch.

I do not know what the plans are for the project with respect to the service 
registry. It's changed a bit between versions, and usually seems like a pain. 
We made the change in a previous upgrade to just drop JSON files on the 
filesystem and have CAS pick those up. It keeps us free of changes in the JPA 
method (which we had been using), and free from management app changes. In 
addition, we can keep service configuration in git, which is extremely nice.

What I gather from that post is you are going to need to change the source code 
of RegisteredServicesReportController either changing that method, or adding 
that method. Looks like it is adding the method. Compile, put into your 
deployment (or download your DB and run locally), and then hit that point to 
get the exported JSON services. If you are running the management application 
in 5.3, I think you can export services as JSON as well, just by clicking a 
bunch of times and possibly doing copy and paste. Depending on your number of 
services, it might be simpler to just export via the management application, 
which I'm assuming that you are using. That would save you from editing code 
and having to deploy a new class file.

Richard

On 3/31/22 09:32, Pablo Vidaurri wrote:
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-5fjan...@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 
tocas-user+u...@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<https://groups.google.com/a/apereo.org/d/msgid/cas-user/133c5bb4-c6cd-4ec6-bf46-e1deaad1ffc4n%40apereo.org?utm_medium=email&utm_source=footer>.


--
- 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 
tocas-user+u...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/75ef5b42-d3b7-366b-8b5b-c784e578b5a2%40ndsu.edu<https://groups.google.com/a/apereo.org/d/msgid/cas-user/75ef5b42-d3b7-366b-8b5b-c784e578b5a2%40ndsu.edu?utm_medium=email&utm_source=footer>.






--
- 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 
tocas-user+unsubscr...@apereo.org<mailto:cas-user+unsubscr...@apereo.org>.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/72d417c2c3c89160ef44b48935e3d894ce937648.camel%40uvic.ca<https://groups.google.com/a/apereo.org/d/msgid/cas-user/72d417c2c3c89160ef44b48935e3d894ce937648.camel%40uvic.ca?utm_medium=email&utm_source=footer>.


-- 
- 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/ea69a407d3fca8b1f7c386671672743783c09650.camel%40uvic.ca.

Reply via email to