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-rc4079734706@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>

(on CHANGELOG.md:8)

This entry is about 330 words, which is documentation rather than a change note. It cites RFC 7628 §3 for certificate verification (that's RFC 6750 §5.3). It also includes the OAUTHBEARER-over-SCRAM precedence, which no PostgreSQL server can trigger. Suggested:

```markdown
* feat: OAUTHBEARER authentication for PostgreSQL 18, set by `oauthToken` or by an `org.postgresql.plugin.OAuthTokenProvider` named in `oauthTokenProviderClassName`. The provider receives `oauthIssuer`, `oauthClientId`, `oauthClientSecret` and `oauthScope`, and the driver does not contact the issuer. `requireAuth` accepts `oauth`. The token is sent only with `sslmode=verify-ca` or `verify-full`, or over GSS encryption, so the default `sslmode=prefer` fails with `OAUTHBEARER authentication requires ...`; `oauthAllowInsecureConnection=true` is for testing [Issue #3816](https://github.com/pgjdbc/pgjdbc/issues/3816) [PR #4251](https://github.com/pgjdbc/pgjdbc/pull/4251)
```

view thread (168+ messages)  latest in thread

Message-ID: <gh-pgjdbc-pgjdbc-4251-rc4079734706@github.com>
Permalink:  ../gh-pgjdbc-pgjdbc-4251-rc4079734706@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