*This problem has been Solved.*
I am forget to insert dependency to *pom.xml* in *management project*.
org.apereo.cas
cas-server-support-jdbc-drivers
${cas.version}
org.apereo.cas
cas-server-support-jpa-service-registry
${cas.version}
Thank you all.
Pada Kamis, 21 Maret 2019
Fahmi,
create-drop is used during initial development of a jpa project when database
design might change regularly. Once database is set, then it gets changed to
update. There is a create option but it will result in errors if the database
already exists. create can be used once and then
Sorry, i am forget attachment.
Strange, I added a service in service management, saved. But there is no
database. But in service management appear. Where is the new service stored?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines:
Hello Ray, thank for your reply.
I changed the configuration:
- Adding cas.jdbc.showSql=true to cas.properties and management.properties
- Adding healthQuery to cas.properties and management.properties
- Change ddlAuto to update
- Rebuilding project cas and management
Log showing (*cas.log*)
Fahmi,
ddlAuto should be set to 'none' or 'update'.
You can also set cas.jdbc.showSql=true to see queries in the logs.
There is also a health query healthQuery='select ...'
Are you running CAS and management server on the same tomcat at the same time
or do you shut one down and start the other?
Thanks for your replies.
I added the service via CAS Service Manangement
(https://sso.example.com/cas-management/manage.html), but it was not saved
in the database. Please help review my CAS configuration (in attachment).
Can you help me please. Thank you.
Pada Rabu, 20 Maret 2019 23.01.06
I am assuming you don't have version control enabled.
After you add the service through console, is your service shown in
Management console list? If so it should be in your service registry
database.
I have the same exception you describe if version control is not enabled
but I am still able
Fahmi,
It sounds like the management server is saving the service to another location,
most likely file system since that is default.
Also, make sure that CAS and management server are pointing to the exact same
service registry. Check spelling of your properties.
Ray
On Wed, 2019-03-20 at
Thanks Facundo for your reply. Regarding "cas.serviceRegistry.jpa.ddlAuto =
create-drop" is only temporary, next time, I will change it to *none *or
*update*.
So, when I go to *https://sso.example.com/cas-management* (*successfully*),
*then
I make 1 new registry service*. *I think it will
Hi Fahmi,
We faced the same issue with managment console. In our case, that error
is not related to the database configuration or the saving action itself
but the GIT versioning functionalitiy of management console
10 matches
Mail list logo
