Re: Connection using ODBC and SSL - Mailing list pgsql-hackers

From Corbit, Dann
Subject Re: Connection using ODBC and SSL
Date
Msg-id AM4PR0202MB275657134F6F96D3E9937AB496FC0@AM4PR0202MB2756.eurprd02.prod.outlook.com
Whole thread Raw
In response to Re: Connection using ODBC and SSL  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Thank you for the assistance.


From: Andrew Dunstan <andrew@dunslane.net>
Sent: Saturday, November 21, 2020 11:14
To: Corbit, Dann <Dann.Corbit@softwareag.com>; PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Cc: Luton, Bill <Bill.Luton@softwareag.com>; Fifer, Brian <Brian.Fifer@softwareag.com>; Lao, Alexander <Alexander.Lao@softwareag.com>
Subject: Re: Connection using ODBC and SSL
 

On 11/20/20 4:54 PM, Corbit, Dann wrote:
>
> I would like to have all my certificates and keys on the same machine
> (localhost for local connections and dcorbit for tcp/ip).
> I found a couple tutorials and tried them but it failed.
> I saw one document that said the common name should be the postgres
> user name and that it should also be the connecting machine name.  Is
> that correct?
> Is there a document or tutorial that explains the correct steps?



I did a webinar about a year ago that went into some detail about what
you need in the CN, where the certificates go, etc.


See
<https://resources.2ndquadrant.com/using-ssl-with-postgresql-and-pgbouncer>
(Yes, this is a corporate webinar, sorry about that)




> Equally important, is there a way to get more complete diagnostics
> when something goes wrong (like WHY did the certificate verify fail)?
>

The diagnostics in the Postgres log are usually fairly explanatory.



cheers


andrew

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: truncating timestamps on arbitrary intervals
Next
From: Tom Lane
Date:
Subject: Re: enable_incremental_sort changes query behavior