doc: clarify that auth. names are lower case and case-sensitive
authorBruce Momjian <[email protected]>
Thu, 21 Jul 2022 17:58:20 +0000 (13:58 -0400)
committerBruce Momjian <[email protected]>
Thu, 21 Jul 2022 17:58:26 +0000 (13:58 -0400)
This is true even for acronyms that are usually upper case, like LDAP.

Reported-by: Alvaro Herrera
Discussion: https://postgr.es/m/202205141521[email protected]

Backpatch-through: 10

doc/src/sgml/client-auth.sgml

index ed077ddb1e6a2a3ee2ce525d4676e271161635ce..d6e1c4c92bfeaa425d01bc55ad0c435c9a216b16 100644 (file)
@@ -381,7 +381,9 @@ hostnossl  <replaceable>database</replaceable>  <replaceable>user</replaceable>
       <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>