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-v40.diff.txt (text/plain)
- v41-0001-Move-PG_MAX_AUTH_TOKEN_LENGTH-to-libpq-auth.h.patch (application/octet-stream) patch v41-0001
- v41-0002-require_auth-prepare-for-multiple-SASL-mechanism.patch (application/octet-stream) patch v41-0002
- v41-0003-libpq-handle-asynchronous-actions-during-SASL.patch (application/octet-stream) patch v41-0003
- v41-0004-Add-OAUTHBEARER-SASL-mechanism.patch (application/octet-stream) patch v41-0004
- v41-0005-squash-Add-OAUTHBEARER-SASL-mechanism.patch (application/octet-stream) patch v41-0005
- v41-0006-XXX-fix-libcurl-link-error.patch (application/octet-stream) patch v41-0006
- v41-0007-DO-NOT-MERGE-Add-pytest-suite-for-OAuth.patch (application/octet-stream) patch v41-0007
On Fri, Jan 10, 2025 at 5:27 AM Peter Eisentraut <peter@eisentraut.org> wrote: > Assuming that uintptr_t is the right underlying type for SOCKET, that > seems ok. Best I can tell, SOCKET is a UINT_PTR (distinct from PUINT) so I think that's correct. > #ifdef WIN32 > > might not work because WIN32 is defined by the PostgreSQL build system, > not by the compiler (see src/include/port/win32.h). Ah, thanks for catching that. Changed to _WIN32. On Thu, Jan 9, 2025 at 2:44 PM Daniel Gustafsson <daniel@yesql.se> wrote: > > > On 9 Jan 2025, at 23:35, Jacob Champion <jacob.champion@enterprisedb.com> wrote: > > I'm sure someone's going to complain at some point, but IMNSHO, the > > fix for them is just to use the same formatting and capitalization as > > the discovery document, and move on. > > Fair enough, I buy that. Maybe the above could be de-opinionated slightly and added as a comment to help others reading the code down the line? Done! On Thu, Jan 9, 2025 at 12:40 PM Daniel Gustafsson <daniel@yesql.se> wrote: > Support for oauth seems to be missing from pg_hba_file_rules() which should be > added in hbafuncs.c:get_hba_options(). Done, and added a basic test for it too. -- v41 handles the feedback since v40, continues fleshing out documentation, and splits out three prefactoring patches: - 0001 moves PG_MAX_AUTH_TOKEN_LENGTH, as discussed upthread - 0002 handles the non-OAuth-specific changes to require_auth (0005 now highlights the OAuth-specific pieces) - 0003 adds SASL_ASYNC and its handling code When I applied Daniel's async_auth_portion patch from earlier, custom flows began double-freeing their socket descriptors. That made logical sense but it wasn't immediately clear to me how to fix it, until I realized that "async authentication state" and "SASL mechanism state" are two different things with different lifetimes, and my previous attempts conflated them. 0003 introduces a cleanup_async_auth() callback, to explicitly free the altsock and its related supporting allocations as soon as it's no longer needed. Not only does this solve the double-free, it removes an extra layer of indirection from 0004 and neatly fixes a TODO where the Curl handles were sticking around for the lifetime of the Postgres connection. Assertions have been added to keep the new internal API consistent. pqSocketCheck() was returning ready if it found buffered SSL data, even if an altsock had been set. I separated the two paths more completely in 0003. The FreeBSD 13.3 image started failing to correctly resolve libcurl package dependencies, leading to missing libssh2 symbols at runtime. And 13.3 went EOL at the end of 2024 -- which is possibly related to the breakage? -- so I seemingly cannot perform a `pkg update` to try to fix things. I've added a hack around this in 0006 that can hopefully be removed again when our Cirrus images transition to 14.2 [1]. Next email will discuss the architectural bug that Kashif found. Thanks, --Jacob [1] https://github.com/anarazel/pg-vm-images/pull/109