TOOLBOX CREATE - the Grant option for the openvpms user should support varying the server name.
Description
When initilializing a new system the toolbox is used to create a database. However there is no option to vary the server that is given the grant permission - it automatically grants to the mysql server only. ie localhost or whatever the mysql host is. This isnt technically correct because the mysql host may not be the tomcat host.
ie: Tomcat Host name: tomcat
Mysql Host name: mysql
Mysql user: openvpms
./toolbox database --create -u root -p openvpms --host mysql
openvpms.properties specifies the user as openvpms - the jbdc is set to jbdc://mysql/openvpms?useSSL=false
The final permissions set applied is
openvpms@mysql NOT opemvpms@tomcat
Use Case: Running containerized applications ephemerally as possible.
Solution: add an option to define the tomcat host in the create script so that when the Grant is done it is locked down to the correct server.
Environment
Docker
Activity
Show:
Benjamin Charlton November 9, 2022 at 1:44 AM
My apologies - clearly I misread the --host options usage.
When initilializing a new system the toolbox is used to create a database. However there is no option to vary the server that is given the grant permission - it automatically grants to the mysql server only. ie localhost or whatever the mysql host is. This isnt technically correct because the mysql host may not be the tomcat host.
ie:
Tomcat Host name: tomcat
Mysql Host name: mysql
Mysql user: openvpms
./toolbox database --create -u root -p openvpms --host mysql
openvpms.properties specifies the user as openvpms - the jbdc is set to jbdc://mysql/openvpms?useSSL=false
The final permissions set applied is
openvpms@mysql NOT opemvpms@tomcat
Use Case: Running containerized applications ephemerally as possible.
Solution: add an option to define the tomcat host in the create script so that when the Grant is done it is locked down to the correct server.