Keycloak 17 Quarkus is not using db-schema parameter properly

Describe the bug

I am trying to deploy Keycloak 17 Quarkus with MariaDb and schema name different from default ‘keycloak’.

I created database with name ‘db4keycloak’ and trying to start Keycloak.

 bin/kc.sh start-dev \
  --db mariadb \
  --db-url-host localhost \
  --db-username keycloak \
  --db-password mypwd \
  --db-schema db4keycloak

And getting error:

022-03-03 21:17:17,040 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (JPA Startup Thread: keycloak-default) HHH000342: Could not obtain connection to query metadata: java.sql.SQLSyntaxErrorException: Could not connect to address=(host=localhost)(port=3306)(type=master) : (conn=45) Unknown database 'keycloak' Keycloak is still trying to connect to default database ‘keycloak’ in JdbcEnvironmentInitiator.

Version

17.0.0

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

1. Install MariaDb
2. Create database user ‘keycloak’ and database ‘db4keycloak’

create database db4keycloak;
GRANT ALL PRIVILEGES ON db4keycloak.* to keycloak@'%' IDENTIFIED BY 'mypwd'; 
GRANT ALL PRIVILEGES ON db4keycloak.* to keycloak@'localhost' IDENTIFIED BY 'mypwd';
flush privileges;

1. Start Keycloak:

 bin/kc.sh start-dev \
  --db mariadb \
  --db-url-host localhost \
  --db-username keycloak \
  --db-password mypwd \
  --db-schema db4keycloak

You will see error message:

[org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (JPA Startup Thread: keycloak-default) HHH000342: Could not obtain connection to query metadata: java.sql.SQLSyntaxErrorException: Could not connect to address=(host=localhost)(port=3306)(type=master) : (conn=50) Unknown database 'keycloak'

Anything else?

No response

[hc42]

I would wait util the merge request is accepted / merged and then close it.

[DGuhr]

to wrap up from what I understood --db-url-database should be used as mysql/mariadb doesn’t have the schema concept and this issue and PR could be closed then. Feel free to re-open when I miss something 😃

note to future me: when we have the ability to show config based on a rule engine (“dependant”), we should remove the db-schema option at runtime when database == mariadb/mysql at buildtime.