Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oC7FW-00014H-H6 for pgsql-docs@arkaria.postgresql.org; Thu, 14 Jul 2022 22:23:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oC7FU-0006xx-5f for pgsql-docs@arkaria.postgresql.org; Thu, 14 Jul 2022 22:23:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oC7FT-0006sx-Um for pgsql-docs@lists.postgresql.org; Thu, 14 Jul 2022 22:23:55 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oC7FM-00080Q-RE for pgsql-docs@lists.postgresql.org; Thu, 14 Jul 2022 22:23:55 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1oC7FH-00Fb7l-Vq; Thu, 14 Jul 2022 18:23:43 -0400 Date: Thu, 14 Jul 2022 18:23:43 -0400 From: Bruce Momjian To: Alvaro Herrera Cc: Tom Lane , "David G. Johnston" , jhebert@micron.com, Pg Docs Subject: Re: Documentation Suggestion Message-ID: References: <202205141521.2nodjabmsour@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0bo/w2W8NaOnarQ7" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0bo/w2W8NaOnarQ7 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Tue, May 24, 2022 at 08:36:18AM -0400, Bruce Momjian wrote: > fOn Sat, May 14, 2022 at 05:21:58PM +0200, Álvaro Herrera wrote: > > On 2022-May-13, Bruce Momjian wrote: > > > Note that valid --auth option values are all lower case, even > > > for authentication types that typically appear as all upper case, > > > e.g., "LDAP". > > > > Yeah, that was my initial thought too. The case-sensitivity is a > > consideration for other things too (such as locale or encoding names), > > but for those we do match the operating system name exactly, rather than > > using our own lower-case version of it, which nobody else uses. > > > > So really the point is not about the fact that it is case sensitive as > > that the case of our name doesn't match the usual one. Maybe the note > > should be "Note that authentication types are all lower case, [even for > > ...]" or something like that. Here is a patch that implements this. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson --0bo/w2W8NaOnarQ7 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="auth.diff" diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index b2a459fb0d..433759928b 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -417,7 +417,9 @@ hostnogssenc database user Specifies the authentication method to use when a connection matches this record. The possible choices are summarized here; details - are in . + are in . All the options + are lower case and treated case sensitively, so even acronyms like + ldap must be specified as lower case. --0bo/w2W8NaOnarQ7--