Hi all -
It turned out to be a Java issue. I must admit we're running some old code,
and recent system updates broke the cas-management service. I had also
switched the authorized/admin users from properties to JSON while
troubleshooting which also goofed things up.
Thanks for reviewing.
-Jeff
Mohamed,
Unfortunately the overlay no longer has a git history, so upgrades are
needlessly complex.
You are making a big upgrade so there will be property name changes.
It is possible to stick with maven, but most of the documentation assumes
gradle. I switched to gradle when it was first an
Jeff,
Was this part of an upgrade?
It could be that a property has changed names. As artur said, you could start
with a vanilla version and the items in one at a time.
There is also the possibility that there is an old/incompatible library hanging
around.
These loggers may help:
Hi,
We are experiencing the same problem on our installation of cas 6.6.11.
Did you manage to correct it?
Now I am where you comment in your message, seeing that changing
cas.authn.saml-idp.core.session-storage-type=TICKET_REGISTRY does not seem
to change anything
Any hint will be
Hello,
I would like to have your feedback about migrations.
What’s the best method? :
1- create a new overlay from scratch and modify property files :
cas.properties
Or
2- modify only the cas.version
Is it required/ recommended to use gradle in overlay ?
My current project is with maven.
