pg.ddx.io  GitHub: pgjdbc/pgjdbc (issues + PRs as email threads)  
help / color / mirror / Atom feed
From: vlsi (@vlsi) <noreply+vlsi@github.com>
To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>
Subject: Re: [pgjdbc/pgjdbc] PR #4251: OAuth implementation
Date: Wed, 23 Sep 2026 06:43:34 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4251-rc4079734673@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>

(on docs/content/documentation/use.md:559)

No PostgreSQL server offers OAUTHBEARER and SCRAM-SHA-256 in one message: the `pg_hba.conf` entry selects one method, and `oauth_get_mechanisms` advertises only OAUTHBEARER. A reader of this paragraph will conclude that setting `oauthToken` makes `password` unusable, or that `requireAuth=scram-sha-256` is needed to keep passwords working. Neither is true: against a SCRAM rule, the driver uses the password even with `oauthToken` set.

Suggested: "The server's `pg_hba.conf` entry selects the method. When it selects `oauth`, the driver sends the token from `oauthToken` or `oauthTokenProviderClassName`; for any other method these properties are ignored." The same claim is in the changelog.

view thread (168+ messages)  latest in thread

Message-ID: <gh-pgjdbc-pgjdbc-4251-rc4079734673@github.com>
Permalink:  ../gh-pgjdbc-pgjdbc-4251-rc4079734673@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox