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, 09 Sep 2026 15:45:36 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4251-rc3970363313@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>
(on pgjdbc/src/main/java/org/postgresql/PGProperty.java)
Section 4 of RFC 7628 is "Examples"; the TLS requirement is in section 3 and section 5. "Confidential channel" is also a phrase the RFC does not use, where it says TLS.
The description string reaches users through `DriverPropertyInfo`, so it is worth more than the javadoc above it. `Default false per RFC 7628` repeats the default that is already the argument on the previous line and gives the reader nothing to act on.
```java
"Allow OAUTHBEARER authentication over a connection encrypted by neither TLS nor GSS. "
+ "RFC 7628, section 3 requires TLS, so enable this for development and testing only."
```
Four of the new descriptions say only what their name says: `OAuth client ID.`, `OAuth client secret.`, `OAuth token scope.`, `OAuth username.`. The fact a user needs is the one `use.md` already carries, that the driver does not contact the issuer and passes these to the `oauthTokenProviderClassName` implementation.