Re: [PoC] Federated Authn/z with OAUTHBEARER
Andres Freund <andres@anarazel.de>
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
Hi, On 2025-06-30 19:42:51 -0400, Andres Freund wrote: > On 2025-07-01 00:52:49 +0200, Daniel Gustafsson wrote: > > > On 30 Jun 2025, at 20:33, Jacob Champion <jacob.champion@enterprisedb.com> wrote: > > > > > > On Mon, Jun 30, 2025 at 10:02 AM Daniel Gustafsson <daniel@yesql.se> wrote: > > >>> On 30 Jun 2025, at 18:58, Andres Freund <andres@anarazel.de> wrote: > > >>> Probably just needs to be added to the installed_targets list. > > >> > > >> Thanks for the report, I'll take a look today to get it fixed. > > > > > > Thanks both! > > > > > > Looking at the installed_targets stuff, though... why do we use `meson > > > install --no-rebuild` in combination with `depends: > > > installed_targets`? Can't we just use Meson's dependency tracking > > > during installation, and avoid this hazard? > > I don't think that's really possible - the dependency tracking is useful to > generate granular *rebuild* information, but doesn't help with the first > build. > > If we had dependency generation for the install target it could be helpful to > discover missing dependencies though. > > > > I suspect it is because without --no-rebuild the quiet target isn't entirely > > quiet. > > No - the issue is that you're not allowed to run ninja while ninja is running, > as that would corrupt it's tracking (and build things multiple times). meson > install --no-rebuild would run ninja to build things... > > > > Still, I was unable to make something that work in all build combinations > > while keeping --no-rebuild (which isn't indicative of it being possible to > > do). > > Hm, what problem did you encounter? I don't think there should be any > difficulty? Ping? Greetings, Andres Freund