@lists.postgresql.org
Subject: Re: Issue with configuration parameter "require_auth"
"Gaisford, Phillip" writes:
> So what would a connection URI using require_auth properly look like? Here’s
> what I have been trying:
> url:
> "postgres://postgres:postgres@local
"Gaisford, Phillip" 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 look
Lane
Date: Wednesday, July 17, 2024 at 11:24 AM
To: Gaisford, Phillip
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Issue with configuration parameter "require_auth"
"Gaisford, Phillip" writes:
> Using golang sqlx.Connect on the client side, the connection fails and
On Wednesday, July 17, 2024, Gaisford, Phillip
wrote:
> I am having trouble using require_auth (https://www.postgresql.org/
> docs/16/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH).
>
>
>
> Using golang sqlx.Connect on the client side, the connection fails and my
> Postgresql 16 server logs the f
"Gaisford, Phillip" writes:
> Using golang sqlx.Connect on the client side, the connection fails and my
> Postgresql 16 server logs the following:
> 2024-07-17 14:42:07.285 UTC [115] FATAL: unrecognized configuration
> parameter "require_auth"
require_auth is a connection parameter, like host
I am having trouble using require_auth
(https://www.postgresql.org/docs/16/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH).
Using golang sqlx.Connect on the client side, the connection fails and my
Postgresql 16 server logs the following:
2024-07-17 14:42:07.285 UTC [115] FATAL: unrecognized c
