Re: [PoC] Federated Authn/z with OAUTHBEARER
Jacob Champion <jacob.champion@enterprisedb.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
meson: Fix install-quiet after clean
- a9ffb35274fb 18.0 landed
- 4ae03be54734 19 (unreleased) landed
-
oauth: Run Autoconf tests with correct compiler flags
- 3d23f68c5529 18.0 landed
- 990571a08b66 19 (unreleased) landed
-
Link libpq with libdl if the platform needs that.
- 4df477153a6b 19 (unreleased) landed
- 7bd752c1fb8e 18.0 landed
-
Doc: correct spelling of meson switch.
- 3faac9d14063 16.9 landed
- 766d2e673342 17.5 landed
- ac557793d478 18.0 landed
-
oauth: Correct SSL dependency for libpq-oauth.a
- 3db68212a393 18.0 landed
-
oauth: Fix Autoconf build on macOS
- 4ea1254f35b2 18.0 cited
-
oauth: Move the builtin flow into a separate module
- b0635bfda053 18.0 landed
-
Remove a stray "pgrminclude" annotation
- 764d501d24ba 18.0 cited
-
oauth: Simplify copy of PGoauthBearerRequest
- 1cf4c56480f8 18.0 landed
-
oauth: Improve validator docs on interruptibility
- 873c0fd67872 18.0 landed
-
oauth: Disallow synchronous DNS in libcurl
- d7e40845f923 18.0 landed
-
oauth: Fix postcondition for set_timer on macOS
- 434dbf6907ec 18.0 landed
-
oauth: Use IPv4-only issuer in oauth_validator tests
- 8d9d5843b55f 18.0 landed
-
Work around OAuth/EVFILT_TIMER quirk on NetBSD.
- c301a0a74a8a 18.0 landed
-
oauth: Fix incorrect const markers in struct
- 03366b61dfe5 18.0 landed
-
Add missing entry to oauth_validator test .gitignore
- 2c53dec7f440 18.0 landed
-
cirrus: Temporarily fix libcurl link error
- 9d9a71002a1c 18.0 landed
-
Add support for OAUTHBEARER SASL mechanism
- b3f0be788afc 18.0 landed
-
libpq: Handle asynchronous actions during SASL
- a99a32e43ed7 18.0 landed
-
require_auth: prepare for multiple SASL mechanisms
- f8d8581ed882 18.0 landed
-
Move PG_MAX_AUTH_TOKEN_LENGTH to libpq/auth.h
- e21d6f297158 18.0 landed
-
Make SASL max message length configurable
- 6d16f9debae0 18.0 landed
-
jsonapi: fully initialize dummy lexer
- 41b023946dfd 18.0 landed
-
common/jsonapi: support libpq as a client
- 0785d1b8b2fa 18.0 landed
-
Remove fe_memutils from libpgcommon_shlib
- f1976df5eaf2 18.0 landed
-
Revert ECPG's use of pnstrdup()
- f0096ef13be2 13.17 landed
- 3557185538fe 14.14 landed
- 2de129b356bf 15.9 landed
- ee2997c678d8 16.5 landed
- e9e05c655069 17.0 landed
- 5388216f6adc 18.0 landed
-
Explicitly require password for SCRAM exchange
- adcdb2c8dda4 17.0 landed
-
Refactor SASL exchange to return tri-state status
- 24178e235ea5 17.0 landed
Attachments
- since-v41.diff.txt (text/plain)
- v42-0001-Move-PG_MAX_AUTH_TOKEN_LENGTH-to-libpq-auth.h.patch (application/octet-stream) patch v42-0001
- v42-0002-require_auth-prepare-for-multiple-SASL-mechanism.patch (application/octet-stream) patch v42-0002
- v42-0003-libpq-handle-asynchronous-actions-during-SASL.patch (application/octet-stream) patch v42-0003
- v42-0004-Add-OAUTHBEARER-SASL-mechanism.patch (application/octet-stream) patch v42-0004
- v42-0005-XXX-fix-libcurl-link-error.patch (application/octet-stream) patch v42-0005
- v42-0006-DO-NOT-MERGE-Add-pytest-suite-for-OAuth.patch (application/octet-stream) patch v42-0006
On Mon, Jan 13, 2025 at 5:00 PM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> So I think what I'm going to need to do is modify v41-0003 to allow
> the mechanism to politely hang up the connection while the flow is in
> progress.
This is done in v42. The rough conversation now looks like this:
Issuer User libpq Backend
| | |
| x -----> x -----> o [1] Startup Packet
| | | |
| | x <----- x [2] OAUTHBEARER Request
| | | |
| | x -----> x [3] Parameter Discovery
| | | |
| | x <----- x [4] Parameters Stored
| | | |
| | x -----> x [5] Finish OAUTHBEARER
x <----> x <----> x | [6] OAuth Handshake
x <----> x <----> x <----- o [7] Server Hangs Up
x <----> x <----> x
| | |
| | x -----> o [8] New Startup Packet
| | | |
| | x <----- x [9] OAUTHBEARER Request
| | | |
o | x -----> x [10] Send Token
| | |
| <----- x <----- x [11] Connection Established
| | |
x <----> x <----> x
x <----> x <----> x [11] Use the DB
. . .
. . .
. . .
The key change is that the client sends the final OAUTHBEARER response
_before_ beginning the OAuth flow, allowing the server to concurrently
close its side of the discovery connection (steps 5-7). This requires
only a single change to the proposed SASL_ASYNC feature in v41-0003:
when a mechanism returns SASL_ASYNC during exchange(), it may also
specify an output response packet to send before switching over to
async auth. (This is similar to how mechanisms may send a response
packet when returning SASL_FAILED.)
That change simplifies the description of the flow a bit, too, and
I've updated the documentation. If an OAuth flow needs to run, two
connections to the server will be made. The only way to skip the
discovery connection now is if a (custom) hook has a token cached.
> This further decouples the lifetimes of the mechanism and
> the async auth -- the async state now has to live outside of the SASL
> exchange --
The only part of the state that I had to move was the token itself,
which now lives in conn->oauth_token. This is cleaned up with a new
pqClear- function, so that it can live across connection attempts and
be proactively cleared from memory after a successful connection.
> but I think it's probably more architecturally sound.
As evidence, this change flushed out a few bugs and provided the basis
to fix every TODO in fe-auth-oauth.c, so I'm pretty happy with it:
- an AuthenticationSASLFinal message is not allowed, as OAUTHBEARER
does not specify any additional server data (this bug goes all the way
back to v1)
- a server is not allowed to switch discovery URLs on a client between
connection attempts
- a server is not allowed to override a previously determined oauth_scope
- the connection is retried only if a conn->oauth_token was not
initially set (this simplifies conn->oauth_want_retry considerably)
- require_auth=oauth will complain if a discovery connection lets the client in
The existing Perl tests were not affected by this refactoring, other
than a latent test bug that got caught with the fallout. The advisory
Python tests (which pin behavior on the wire) needed more changes.
I've also added some tests to 002_client.pl which have the custom hook
misbehave in various ways and pin the expected error messages.
v41-0005 has probably outlived its usefulness by now, and I've folded
those changes into v42-0004.
Thanks!
--Jacob