Re: [PoC] Federated Authn/z with OAUTHBEARER
Wolfgang Walther <walther@technowledgy.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
Jacob Champion: > (The [2] link is missing, I think.) Ah, sry. This is the link: https://github.com/wolfgangwalther/nixpkgs/commits/postgresql-libpq-curl/ It's the last two commits on that branch. > I'm confused by this -- the build produces staticlibs alongside the > dynamically linked ones, so that's what I've been testing against. > What different options do you pass to configure for a "statically > linked build"? It's not so much the options, but more that for this build there are no shared libs available at buildtime at all. You can consider it a "fully static system". So in your case, you'd always do the configure test with shared libs, but I can't. The build system passes --enable-static and --disable-shared to configure, but both of those are ignored by configure, as indicated by a WARNING immediately. >> Not unless there is some magic in PKG_CHECK_MODULES I've never heard >> of (which is entirely possible!). Furthermore I imagine that the >> transitive dependencies of all its dependencies are not added either. IIUC, the transitive dependencies would be part of libcurl's Libs.private / Requires.private (assuming that file is correctly created). So that would be taken care of, I guess. > Does your build method currently work for dependency forests like > libgssapi_krb5 and libldap? (I want to make sure I'm not accidentally > doing less work than we currently support for those other deps, but > I'm also not planning to add more feature work as part of this > particular open item.) We currently build libpq with neither libldap, nor libkrb5, at least for the static case. But I just tried on the bigger postgresql package and force-enabled libldap there for the static build - it fails in exactly the same way. So yes, not related to your patch. I do understand that PostgreSQL's autoconf build system is not designed for "static only", I am certainly not expecting you to fix that. I think meson will do better here, but I was not able to make that work, yet. >> When I do "make -C src/interfaces/libpq-oauth", I get this error: >> >> make: *** No rule to make target 'oauth-curl.o', needed by >> 'libpq-oauth-18.so'. Stop. > I cannot reproduce this. The CI seems happy, too. Is this patch the > only modification you've made to our build system, or are there more > changes? We apply another patch to change the default socket directory to /run, but that's certainly unrelated. All the other custom stuff only kicks in afterwards, in the installPhase, so unrelated as well. I just tried the same thing on the bigger postgresql package, where the full build is run and not only libpq / libpq-oauth. It fails with the same error. No rule for oauth-curl.o. > I'm about to rewrite this part somewhat, so a deep dive may not be very helpful. OK. I will try to get meson running, at least enough to try this patch again. Maybe that gives better results. Thanks, Wolfgang