Re: Improve OAuth discovery logging - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Improve OAuth discovery logging
Date
Msg-id 7DB528BA-C7A0-4B23-890C-5332FB35A16E@yesql.se
Whole thread Raw
In response to Improve OAuth discovery logging  (Zsolt Parragi <zsolt.parragi@percona.com>)
Responses Re: Improve OAuth discovery logging
List pgsql-hackers
> On 11 Feb 2026, at 20:24, Zsolt Parragi <zsolt.parragi@percona.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




pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: make ExecInsertIndexTuples arguments less bad
Next
From: Nathan Bossart
Date:
Subject: add warning upon successful md5 password auth