
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
postgres v15 sslmode=verify-full not working
We use Qlik Sense Enterprise.
It is impossible to create a data connector to Postgres when using the postgres sslmode=verify-full mode. It is not clear where to specify the paths to the three keys (root.crt, open.crt, private.key).
The standard Qlik odbc date connector to Postgres is used.
1. Qlik Sense November 2023 Patch 2 - 14.159.6
2.Postgres 15
3. Tried with different separators (& and ;). jdbc connection to DBeaver takes place with this connection string
postgresql://tech_user:***@10.50.220.21:5432/postgres?sslmode=verify-full&postgresql://tech_user:***@10.50.220.21:5432/postgres?sslmode=verify-full&sslrootcert=/home/alanuccio /projects/freedom/some_work_stuff/root.crt&sslcert=/home/alanuccio/projects/freedom/some_work_stuff/tech_user.crt&sslkey=/home/alanuccio/projects/freedom/some_work_stuff/tech_user.key

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I think after a quick read of your topic it's because the SSL certificate doesn't specify your hostname.
You can try to set SSL mods to sslmode=verify-ca or sslmode=require instead of verify-full, or use a certificate with the correct hostname.
Kind regards
