If you mean authenticate using a client-certificate, then see http://www.postgresql.org/docs/9.1/static/libpq-ssl.html and 31.17.2. Client Certificates. Basically, Postgres (libpq) will handle this automatically if you store your cert in ~/.postgresql/postgresql.crt. Libzdb still requires that you specify a username and password in the connection URL though.
Details: Previously, as far as I remember, libpq and PQconnectdb() which libzdb use, did not support auth via client cert so setting client cert as a URL-parameter is not supported. I see from the documentation (http://www.postgresql.org/docs/9.1/static/libpq-connect.html) that this is now possible and we might support this in a later version.
On 07 Apr 2016, at 21:52, Vicki Ma vma@akamai.com wrote:
Hi,
I plan to use libzdb for connection pooling, but I am not sure if I can connect to the connection pool using user certificate.
In the document, it specifies how to connect to Postgresql database.
postgresql://localhost:5432/test?user=root&password=swordfish
Can I pass the following: postgresql://user:secret@localhost I did not see the options mentioning connecting database using certificates.
http://tildeslash.com/libzdb/api-docs/postgresoptions.html
Thanks very much, Vicki Ma