I also tried adding -db=postgres after RUN /opt/keycloak/bin/kc. Hello All, As I have tried many ways to solve this problem, yet still fail. t prebuilt-keycloakĪnd then docker run -p 8443:8443 prebuilt_keycloak Anything else?Īs of the time of writing, the "latest" is "17.0.0" View Profile View Forum Posts Private Message Junior Member Join Date Oct 2013 Posts 23.
Jdbc no suitable driver found driver#
Show Printable Version 04-17-2015, 10:09 AM 1. Re: xdb No suitable driver found for jdbc:oracle:thin ERROR Hi Swagata, I have switch java on OS to java 8, copied the ojdbc8.jar accordingly on both the subscriber and publisher,restarted both the servers. :port/ database I advise anyone with the same problem to check the driver documentations for the exact syntax. Invalid JNDI connection bdc : No suitable driver found for jdbc:sqlserver Results 1 to 5 of 5 Thread: Invalid JNDI connection bdc : No suitable driver found for jdbc:sqlserver. SOLVED: Okay apparently I got the syntax wrong and for my driver its supposed to be: jdbc:mysql:// host ,failoverhost. One fun thing is, It works when run as tomcat7 server.(which means run by localhost). EDIT: I updated to 3.6.1 and registerJdbcDriver is found but does not solve the problem. And of course I set Bulid path mssql-jdbc-6.2.2.jre8.jar into 'C:\Program Files\Java\jre1.8.091\lib\ext' But didnt work. # change these values to point to a running postgres instanceĮNV KC_DB_URL=jdbc:postgresql://database:5432/keycloakĮNTRYPOINT But when I connect to the App service it always says 'no suitable driver found for jdbc/mssql' like this.
![jdbc no suitable driver found jdbc no suitable driver found](https://i.stack.imgur.com/Fmj4z.png)
Jdbc no suitable driver found password#
RUN keytool -genkeypair -storepass password -storetype PKCS12 -keyalg RSA -keysize 2048 -dname "CN=server" -alias server -ext "SAN:c=DNS:localhost,IP:127.0.0.1" -keystore conf/server.keystore If you use a driver which is not JDBC 4.0. # for demonstration purposes only, please make sure to use proper certificates in production instead In order to solve this error, you need the MySQL JDBC driver e.g. FROM quay.io/keycloak/keycloak-x:latest as builderĬOPY -from=builder /opt/keycloak/lib/quarkus/ /opt/keycloak/lib/quarkus/