PostgreSQL SSL error when connecting with DataIKU

Registered Posts: 2 ✭✭✭

Hello hello,

When trying to connect a local postgreSQL database to DataIKU, I obtain the error "Server does not support SSL".

I also tried the method bypassing the certificates by adding the parameters sslfactory, org.postgresql.ssl.NonValidatingFactory but the outcome remains the same.

As the SSL has been activated on my database and the certificates generated, I do not understand what this error means.

Here is my configuration

- Windows 11
- PostgreSQL 11 installed on my C drive
- DataIKU 9.0.1 installed on Oracle VM

Any help on solving this issue will be appreciated.

Thank you


Operating system used: Windows 11


Operating system used: Windows 11

Welcome!

It looks like you're new here. Sign in or register to get started.

Answers

  • Dataiker, Dataiku DSS Core Designer, Dataiku DSS ML Practitioner, Dataiku DSS Adv Designer, Registered Posts: 1,253 Dataiker

    Hi,

    Can you confirm the exact properties you added to the connection in DSS?

    Can you try the following :

    Screenshot 2022-02-11 at 12.01.01.png

    ssl = true
    sslfactory=org.postgresql.ssl.NonValidatingFactory

    sslmode=require may not work on the current version of the JDBC driver.

    Thanks

  • Registered Posts: 2 ✭✭✭

    Hello,

    Apologize for the late answer.

    Here are the properties I added in the connection:

    Capture d’écran 2022-02-22 140100.png

    ssl --> true

    sslfactory --> org.postgresql.ssl.NonValidatingFactory

    I also tested without the sslfactory property, but the results remain unchanged

    Moreover, we tested with sslmode = require, prefer, allow.

    Still, the error stays the same

    Thank you in advance for your assistance

  • Dataiker, Dataiku DSS Core Designer, Dataiku DSS ML Practitioner, Dataiku DSS Adv Designer, Registered Posts: 1,253 Dataiker

    Hi Stephen,

    Would be able to open a chat or support ticket: https://doc.dataiku.com/dss/latest/troubleshooting/obtaining-support.html

    With the backend.log after reproducing the issue to see if that provides more information perhaps.

    Thanks,

    Alex

Welcome!

It looks like you're new here. Sign in or register to get started.

Welcome!

It looks like you're new here. Sign in or register to get started.