Re: Issue with configuration parameter "require_auth" - Mailing list pgsql-general

From Gaisford, Phillip
Subject Re: Issue with configuration parameter "require_auth"
Date
Msg-id DM4PR84MB151709CC219E9ABDA4506EAF8DA32@DM4PR84MB1517.NAMPRD84.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Issue with configuration parameter "require_auth"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

I think Tom is right.

 

I am using v5.6 of https://github.com/jackc/pgx

 

I quick read of the code reveals no awareness of require_auth, so I have filed an issue with the project.

 

From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wednesday, July 17, 2024 at 1:11
PM
To: Gaisford, Phillip <phillip.gaisford@hpe.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Issue with configuration parameter "require_auth"

"Gaisford, Phillip" <phillip.gaisford@hpe.com> writes:
> So what would a connection URI using require_auth properly look like? Here’s what I have been trying:

> url: "postgres://postgres:postgres@localhost:5432/aioli?require_auth=password&application_name=aioli-controller&sslmode=disable&sslrootcert=",

Hm, that looks right (and behaves as-expected here).

What version of what client-side stack are you using?  For me, libpq 16
and up recognize this parameter, while older versions fail with

psql: error: invalid URI query parameter: "require_auth"

If you're using some other client driver, maybe it doesn't know this
parameter and guesses that it should be passed to the server.

                        regards, tom lane

pgsql-general by date:

Previous
From: Kashif Zeeshan
Date:
Subject: Re: Planet Postgres and the curse of AI
Next
From: Adrian Klaver
Date:
Subject: Re: Planet Postgres and the curse of AI