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

Following up here since I saw PR #4251 great to see this has real momentum, thank you for the work on it. Wanted to flag a concrete use case for prioritization: we're standing up a self-managed PostgreSQL 18 instance (managed PG18 isn't available from our cloud provider yet) and already use Microsoft Entra ID (Azure AD) for SSO across the rest of our platform. Native OAUTHBEARER support is exactly what we'd want for database login too same identity provider, no separate DB credentials to manage or rotate. We're currently blocked purely because our GUI client (DBeaver) depends on pgjdbc for its PostgreSQL connections.

I saw the maintainers' note that this is waiting on a patch release before it can merge — is there a rough sense of when that's expected? Also happy to help test the token-provider flow against a real Entra ID tenant once it's mergeable, if that's useful for validation before release.

view thread (168+ messages)  latest in thread

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