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, 09 Sep 2026 15:45:36 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4251-rc3970363347@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>

(on .github/workflows/matrix.mjs)

RFC 7632 is "Endpoint Security Posture Assessment: Enterprise Use Cases". The document you want is 7628, and its TLS requirement is in section 3.

```js
// OAUTHBEARER must run over TLS (RFC 7628, section 3), so OAuth rows need ssl=yes.
```

Two more in this block. The comment above line 357 says the Keycloak container exists only for PG 18 and up, and `quay.io/keycloak/keycloak:26.7` has no PostgreSQL version tied to it; the constraint belongs to `pg-oidc-validator-pgdg18.deb`. And near line 600, `// Route every connection through OAuth` overstates what `TestUtil.addOAuthProperties` does, which is to redirect connections of the default user that have no OAuth configured already.

view thread (168+ messages)  latest in thread

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