From: | "Mark Williams" <markwillimas(at)gmail(dot)com> |
---|---|
To: | "'Wim Bertels'" <wim(dot)bertels(at)ucll(dot)be>, <pgsql-admin(at)lists(dot)postgresql(dot)org>, <s(dot)dunand(at)sirap(dot)fr> |
Subject: | RE: Setting up SSL for postgre |
Date: | 2018-08-23 16:53:55 |
Message-ID: | 09bf01d43b01$e12213e0$a3663ba0$@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Wim,
I did intend Cert aut (at least I think I did!).
Still cannot connect to postgre database from my client app using FireDAC. I
can connect fine from PGAdmin3 on the same machine using the same
certificates.
The call made by FireDAC to libPQ.Dll is the following:
PQconnectdb [ConnInfo=hostaddr=192.168.0.12 port=5432 dbname=rees
user=postgres password=*** connect_timeout=10 sslmode=require
sslrootcert=C:\ProgramData\MWC\Viewer\Certs\root.crt
sslcert=C:\ProgramData\MWC\Viewer\Certs\postgresql.crt
sslkey=C:\ProgramData\MWC\Viewer\Certs\postgresql.key password=1234,
Result=$0000000003B262B0]
13222564840001 17:41:04.681 . ERROR: connection requires a valid client
certificate [Status=1]
The SSLmode is set to require when I connect with PGAdmin. So presumably,
there is no problem with the certificates. Is there anything that jumps out
from the FireDAC output as to why the SSL connection doesnt work?
Many thanks,
Mark
__
From: Wim Bertels <wim(dot)bertels(at)ucll(dot)be>
Sent: 22 August 2018 09:19
To: Mark Williams <markwillimas(at)gmail(dot)com>;
pgsql-admin(at)lists(dot)postgresql(dot)org; s(dot)dunand(at)sirap(dot)fr
Subject: Re: Setting up SSL for postgre
Hallo Mark,
as i quickly read the error message in your question,
these we're my first suggestions.
either
* did you intent cert aut for the postgres user?
* u use a selfsigned certificate, hence software that checks for the
validity will fail or ask for this
** using for example the free, but official letsencrypt certificates this
should be solved
hth,
Wim
_____
Van: Mark Williams <markwillimas(at)gmail(dot)com <mailto:markwillimas(at)gmail(dot)com> >
Verzonden: maandag 20 augustus 2018 16:51
Aan: Wim Bertels; pgsql-admin(at)lists(dot)postgresql(dot)org
<mailto:pgsql-admin(at)lists(dot)postgresql(dot)org> ; s(dot)dunand(at)sirap(dot)fr
<mailto:s(dot)dunand(at)sirap(dot)fr>
Onderwerp: RE: Setting up SSL for postgre
Hi,
Sorry I dont understand what you are suggesting re the pg_hba file.
__
From: Wim Bertels < <mailto:wim(dot)bertels(at)ucll(dot)be> wim(dot)bertels(at)ucll(dot)be>
Sent: 20 August 2018 14:30
To: <mailto:pgsql-admin(at)lists(dot)postgresql(dot)org>
pgsql-admin(at)lists(dot)postgresql(dot)org; <mailto:s(dot)dunand(at)sirap(dot)fr>
s(dot)dunand(at)sirap(dot)fr
Subject: Re: Setting up SSL for postgre
pg_hba.conf
# TYPE DATABASE USER CIDR-ADDRESS METHOD
# IPv4 local & remote connections:
host all all 127.0.0.1/32 trust
hostssl all postgres 0.0.0.0/0 cert
cert method for auth, hence this behaviour (client cert..)
extra tip:
<https://duckduckgo.com/?q=letsencrypt+postgresql>
https://duckduckgo.com/?q=letsencrypt+postgresql
for official server side certificates
mvg,
Bertels Wim
Mark
__
This page helped me :
<https://www.depesz.com/2015/05/11/how-to-setup-ssl-connections-and-authenti
cation/>
https://www.depesz.com/2015/05/11/how-to-setup-ssl-connections-and-authentic
ation/
Best regards,
Stéphane
From | Date | Subject | |
---|---|---|---|
Next Message | AYahorau | 2018-08-24 08:49:39 | Re: Logical replication monitoring |
Previous Message | Tom Lane | 2018-08-23 14:22:32 | Re: Call Function from within Function - parent / dispatch |