Ray, Thanks for your answer.
I think that the problem is also on 6.6.0+ versions.
The embedded properties are loaded after external files.
In the previous versions, only yaml files were considered and since they are empty by default, there is no impact on the defined properties in the external files.
Is there a way to override the DefaultCasConfigurationPropertiesSourceLocator, so I will change the order of loading properties?
Now the only workaround that I found is to define system properties on the cas startup script : -
Dcas.server.name and jpa service registry properties, otherwise it will load an empty memory database for cas management...
Best Regards.