| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Subject: | Re: Improve OAuth discovery logging |
| Date: | 2026-02-11 19:30:21 |
| Message-ID: | 7DB528BA-C7A0-4B23-890C-5332FB35A16E@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 11 Feb 2026, at 20:24, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
> Not sure if this is the best way to handle it or not, but it seems the
> cleanest to me, as the SASL code already had these return codes and
> this way the patch doesn't introduce anything OAuth specific to the
> logic.
Off the cuff this seems reasonable from technical standpoint. However, is the
below message of LOG level interest to an admin?
+ ereport(LOG,
+ errmsg("OAuth issuer discovery requested by user \"%s\"",
Is this valuable to administrators in production, or should this perhaps be a
DEBUGx level logging?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-02-11 19:52:33 | add warning upon successful md5 password auth |
| Previous Message | Fabrízio de Royes Mello | 2026-02-11 19:29:33 | Re: make ExecInsertIndexTuples arguments less bad |