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 <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
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 <replaceable>database</replaceable> <replaceable>user</replaceabl
<para>
Specifies the authentication method to use when a connection matches
this record. The possible choices are summarized here; details
- are in <xref linkend="auth-methods"/>.
+ are in <xref linkend="auth-methods"/>. All the options
+ are lower case and treated case sensitively, so even acronyms like
+ <literal>ldap</literal> must be specified as lower case.
<variablelist>
<varlistentry>
