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-v37.diff.txt (text/plain)
- v38-0001-Add-OAUTHBEARER-SASL-mechanism.patch (application/octet-stream) patch v38-0001
- v38-0002-DO-NOT-MERGE-Add-pytest-suite-for-OAuth.patch (application/octet-stream) patch v38-0002
On Wed, Nov 27, 2024 at 9:27 AM Daniel Gustafsson <daniel@yesql.se> wrote: > Thanks for the updated version, it's really starting to take good shape. A few > small comments on v37 from a a first quick skim-through: Applied in v38, thanks! > fail_validator.c seems to have the #include list copied from validator.c and > pulls in unnecessarily many headers. Oops, thanks for the cleanup. > In validate() I wonder if we should doublecheck that have a a proper set of > validator callbacks loaded just to make even more sure that we don't introduce > anything terrible in this codepath. Seems good. I think this part of the API is going to need an ABI-compatibility pass, too. For example, do we want a module to allocate the result struct itself (which locks in the struct length)? And should we have a MAGIC_NUMBER of some sort in the static callback list, maybe? -- Now that our JSON API can be put into "leakproof" mode [1], I can fuzz the parser implementations. libfuzzer has been able to find one known issue, plus two more that I was unaware of: 1. Duplicate fields caused the previous field values to leak. (This was the documented FIXME; we now error out in this case.) 2. The array-of-strings parsing had a subtle logic bug: if field "a" was expected to be an array of strings, we would also accept the construction `"a": "1"` as if it were equivalent to `"a": ["1"]`. This messed up the internal tracking and tripped assertions. 3. handle_oauth_sasl_error() was leaking all of its parsed fields if they didn't get hooked into the PGconn struct before a failure. All three are fixed in v38; I will keep working on expanding the amount of code covered by my fuzzers. Additionally, the following pieces of feedback has been addressed: - We now validate the incoming JSON as UTF-8 before lexing it, to prevent invalid multibyte sequences from sneaking through in the strings [2]. Still need to determine how \uXXXX sequences will interact with the more punishing client encodings in error messages. - --with-builtin-oauth/-Dwith_builtin_oauth has been renamed --with-libcurl/-Dlibcurl, and the Autoconf side uses PKG_CHECK_MODULES exclusively. - markPQExpBufferBroken has been replaced with termPQExpBuffer in append_urlencoded() - the anonymous union has been named - pg_be_oauth_mech uses a designated initializer Next up, the many-many documentation requests, now that the fuzzers can run while I write. Thanks, --Jacob [1] https://postgr.es/c/5c32c21afe6 [2] https://postgr.es/m/ZjmjPyA29dIJjmjI%40paquier.xyz