CAS 5 and 6, consent JDBC database name from "ConsentDecision" to "Consent_Decision" issue and fix

[Andy Ng]

Hi all,

During migration from CAS 5 to CAS 6, I encountered an issue:

• My consent table, originally called `ConsentDecision` , is now renamed to `Consent_Decision`
• Moreover, the fields name is also changed, same pattern

We have found a solution and want to share here:

• it is actually changes in Spring boot library behavior, detail see this 
  • https://stackoverflow.com/questions/29087626/entity-class-name-is-transformed-into-sql-table-name-with-underscores
• Adding this properties should work now:
  • spring.jpa.hibernate.naming.physical-strategy=org.hibernate.boot.model.naming.PhysicalNamingStrategyStandardImpl
    

Add this here in case other encounter same issue, cheers!

Regards,

Andy

[Pablo Vidaurri]

I'm having the opposite issue with CAS 6.3.2

My table and column names in db are snake_case.

My classes and properties are CamelCase.

Cas is simply lower casing the names and they are not found in the db

I have a custom database source that I want to use CamelCase to SnakeCase. So I created my own naming strategy class. But it is not being picked up.

custom.mydbsource.physical-naming-strategy-class-name=org.apereo.cas.hibernate.CustomSnakecasePhysicalNamingStrategy

In my DataSource setup, do I have to explicitly need to read this property and call a setter for it?

I do not wish to change the naming strategy for all my db sources especially for those used and maintained by CAS. I only want to use this custom naming strategy on my custom datasource.

-psv

[Pablo Vidaurri]

I was able to get this resolved by adding it as a property in my DB Configuration:

String namingStrategy = customProperties.getEbizdbsource().getPhysicalNamingStrategyClassName();

Properties properties = new Properties();

properties.setProperty("hibernate.physical_naming_strategy", namingStrategy);