Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vqFv2-007SzO-1E for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Feb 2026 19:30:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vqFv1-005Ljw-22 for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Feb 2026 19:30:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vqFv1-005Ljg-0l for pgsql-hackers@lists.postgresql.org; Wed, 11 Feb 2026 19:30:36 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vqFv0-00000000CTZ-0bK9 for pgsql-hackers@postgresql.org; Wed, 11 Feb 2026 19:30:35 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 2F8E8557C37 for ; Wed, 11 Feb 2026 20:30:33 +0100 (CET) Received: from s981.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 1B08E555E3C; Wed, 11 Feb 2026 20:30:33 +0100 (CET) Received: from localhost (unknown [172.22.191.5]) by s981.loopia.se (Postfix) with ESMTP id 1950022B1775; Wed, 11 Feb 2026 20:30:33 +0100 (CET) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s471.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s981.loopia.se ([172.22.191.6]) by localhost (s471.loopia.se [172.22.190.35]) (amavis, port 10024) with LMTP id qnL8_aFitlkd; Wed, 11 Feb 2026 20:30:32 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s981.loopia.se (Postfix) with ESMTPSA id 7A8C522B1704; Wed, 11 Feb 2026 20:30:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1770838232; bh=GzU22MVoiWj5BmC6Che+i5F26hUHDKaYC2J/ExIGRK8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=sKRKOhZ4fZn9hEqE6RXYQds8TPfsEfDYSq/N60ahGHtwnAptV9uv+FXofl6sVw8qR PS2NlUvVMH2sbLBu++KlWFCXV6I9eaFCRHXOL0yvhVG60YJimJW4a2B51owz83t1Zd uFQ2KRI9n4rfsZQ4PaJJK6vZ8eEXuDN8o/n9fusBEQturKsZB6oSClaps6V5DnnZDM LubfvERy+Fdx61gyDYA+dHS3g5jyYsgrpljIt2s2CLDZESqpNtvzOOCB/DrG7de2tz Mbwt8CVar/GAiY2WLThQvj3Stk15BFZxMI8JUNeuFfyFH1SpqD3wABrQuTuBggBsAy paJO4TBXNSwsg== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\)) Subject: Re: Improve OAuth discovery logging From: Daniel Gustafsson In-Reply-To: Date: Wed, 11 Feb 2026 20:30:21 +0100 Cc: PostgreSQL Hackers , Jacob Champion Content-Transfer-Encoding: quoted-printable Message-Id: <7DB528BA-C7A0-4B23-890C-5332FB35A16E@yesql.se> References: To: Zsolt Parragi X-Mailer: Apple Mail (2.3776.700.51.11.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 11 Feb 2026, at 20:24, Zsolt Parragi = 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