| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add support for OAUTHBEARER SASL mechanism |
| Date: | 2025-04-01 13:11:51 |
| Message-ID: | CB1D7ED6-0A7C-4B3E-84E4-72E9576E9AAD@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
> On 1 Apr 2025, at 15:03, Christoph Berg <myon(at)debian(dot)org> wrote:
> With the libpq-oauth split, this makes even more sense because
> building a library that always throws an error isn't very useful.
> (Don't build that file at all if the feature doesn't work.)
After the split, configure/meson should fail if the libcurl dependency isn't
satisfied or if the platform isn't supported.
> Since oauth/curl have some security implications, would it make more
> sense to call the switch --enable-oauth (-Doauth) so users could
> control better what features their libpq is going to have? Perhaps
> some other feature (pg_service as URL?) is going to need libcurl as
> well, but it should be configurable separately.
Perhaps --with-oauth-client for the opt-in libpq-oauth?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2025-04-01 13:30:27 | pgsql: Remove a stray "pgrminclude" annotation |
| Previous Message | Christoph Berg | 2025-04-01 13:03:25 | Re: pgsql: Add support for OAUTHBEARER SASL mechanism |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcos Pegoraro | 2025-04-01 13:14:58 | Re: add function argument name to substring and substr |
| Previous Message | Peter Eisentraut | 2025-04-01 13:04:37 | Re: PRI?64 vs Visual Studio (2022) |