| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Antonin Houska <ah(at)cybertec(dot)at>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PoC] Federated Authn/z with OAUTHBEARER |
| Date: | 2024-10-29 17:41:27 |
| Message-ID: | 009AF2BB-F169-498C-A4DE-73D8E3001537@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 29 Oct 2024, at 17:40, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>
> On Tue, Oct 29, 2024 at 3:52 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>> Currently we don't support any conditional compilation which only affects
>> backend or frontend, all --without-XXX flags turn it off for both.
>
> I don't think that's strictly true; see --with-pam which affects only
> server-side code, since the hard part is in the server. Similarly,
> --with-oauth currently affects only client-side code.
Fair, maybe it's an unwarranted concern. Question is though, if we added PAM
today would we have done the same?
> But in any case, that confusion is why I'm proposing a change to the
> option name.
+1
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2024-10-29 17:45:02 | Re: MultiXact\SLRU buffers configuration |
| Previous Message | Tristan Partin | 2024-10-29 17:40:06 | Re: RFC: Extension Packaging & Lookup |