Our application should access the database with a user that can only manipulate data and another user should be used as schema owner to run Liquibase with more authorizations . This appraoch reduces security risks in case of breach. Therefore, we need to have 2 different users, one for Liquibase and for our JMIX V2 application.
We looked at your documentation Springboot and we tried to connecto to our Oracle database as mentioned.
I may have an idea, how about using spring profiles?
Make one profile with an admin level access rights, that you can run when updating the database structure, and another for normal usage.
Be sure to test this, because Jmix usually expects full access rights to its database.
This option seems to work. Thanks for the hint!. It is not perfect because we need to make the deployment twice but at least is a workaround.
If this requirement is requested by other customers, it would be good if the team can have a look at this topic and make possible to run liquibase and the application with 2 user in the same deployement.
Note that this affects only the runtime execution of the Liquibase changelogs by the application. Studio will continue using the main datasource configuration.