Ray, thank you for your advice.
Yes I’m just finishing validating 6.6.15. But will move to 7 soonly.
The registeredServices endpoints are now available in my installation. I
moved the management.endpoint.* properties from application.properties to
cas.properties and they become available. I have
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
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 a écrit :
> To get a list of all properties (and some defunc
Hello,
I didn’t find such a service in cas 5 but there is this blog post that
explains service migration solution. It’s the blog of Misagh so could be
used as a reference.
https://fawnoos.com/2021/01/19/cas53-service-registry-migration-to-cas63/
For me I will use manual export import because it
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:
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:
But i meant tables for service registry. What is the best method to migrate
all services stored on mysql db from 5.3 to 6.6. I know we can export each
service to json format and probably (maybe some changes is required) we can
import them to 6.6. We can do it from cas management dashboards or put
s
The documentation for 5.1.x is all off-line now, can you tell us how to
enable the /status/services/export endpoint? We have the status dashboard
endpoint but the services/export gives a 404 error. We're in the same
process of moving from 5.1.5 to 6.6.13 and any help moving the services
would b
Can you explain more about what was your minor change on exported Service
entries? I want to do same thing for migrating from cas 5.3 to 6.6
On Wednesday, June 29, 2022 at 1:44:27 AM UTC+4:30 Dave Steiner wrote:
> We are currently upgrading from v5 to v6 and use JPA like you are. What
> we are
Hi Steine, does it works your test ?
Il giorno martedì 28 giugno 2022 alle 23:14:27 UTC+2 steine...@gmail.com ha
scritto:
> 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 ou
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/regi
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 jus
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
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-7 fjan...@gmail.com wrote:
> Thank you for the response.
>
> We actually use CAS Management application,
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
Ah, sorry ... service registry, not ticket registry.
I keep service JSON files so I dont have to deal with table changes. I
never saw the benefit of loading services in DB as I don't want others with
access to fudge with the config and placing the services files in git is
convenient for disaste
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 cha
17 matches
Mail list logo
