Re: dispchar for oauth_client_secret - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: dispchar for oauth_client_secret
Date
Msg-id CAOYmi+kGgZEHdkH=w6mTa1Z9vSz3stX4qt6ws-tEDem7DT2k1w@mail.gmail.com
Whole thread Raw
In response to Re: dispchar for oauth_client_secret  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
On Tue, Apr 15, 2025 at 11:11 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> On Wed, 16 Apr 2025 at 02:03, Jacob Champion
> <jacob.champion@enterprisedb.com> wrote:
> > Thank you for saying something; I'd hallucinated that srvoptions was
> > limited to the server owner, and that's not true. It's pg_user_mapping
> > that has the protection.
>
> FWIW, I have some ideas on being able to store secrets in a server in
> a safe way. I'll probably start a thread on that somewhere in the next
> few months.

Sounds great!

Attached is my proposed fix. 0001 disables use of the new oauth_*
options in our FDWs. 0002 changes dispchar.

Thanks,
--Jacob

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Changing shared_buffers without restart
Next
From: Jacob Champion
Date:
Subject: Re: jsonapi: scary new warnings with LTO enabled