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: Tue, 14 Jul 2026 10:14:13 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4251-c4968047510@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>

Great update so far.

I'm not sure regarding pass-through only connection properties (oauthIssuer, oauthClientId, oauthClientSecret, oauthScope, oauthUsername). The driver does not use them, yet they become the public API.

---

Could you please clarify the reason you exclude oath+ssl?
It would be great to have the test coverage for successful oauth + ssl.

---

CI execution produces a lot of warnings:

```
UpdateableResultTest > testUpdateRowWithLocalDateTime() STANDARD_ERROR
    июл 06, 2026 1:07:44 AM org.postgresql.core.v3.OAuthAuthenticator checkTransportEncryption
    WARNING: OAUTHBEARER is being used over an unencrypted connection. This violates RFC 7628 §4. DO NOT USE THIS CONFIGURATION IN PRODUCTION!
```

Could you please make it so successful execution does not produce false warnings/stdout messages?

view thread (168+ messages)  latest in thread

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