Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ef40ab7

Browse files
committed
docs: clarify the interaction of clientcert and cert auth.
This is the first paragraph change of master-only commit 253f1025da. Backpatch-through: PG 12-13 only
1 parent d1c23d7 commit ef40ab7

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

doc/src/sgml/client-auth.sgml

+4-7
Original file line numberDiff line numberDiff line change
@@ -2042,13 +2042,10 @@ host ... radius radiusservers="server1,server2" radiussecrets="""secret one"",""
20422042
</para>
20432043

20442044
<para>
2045-
In a <filename>pg_hba.conf</filename> record specifying certificate
2046-
authentication, the authentication option <literal>clientcert</literal> is
2047-
assumed to be <literal>verify-ca</literal> or <literal>verify-full</literal>,
2048-
and it cannot be turned off since a client certificate is necessary for this
2049-
method. What the <literal>cert</literal> method adds to the basic
2050-
<literal>clientcert</literal> certificate validity test is a check that the
2051-
<literal>cn</literal> attribute matches the database user name.
2045+
It is redundant to use the <literal>clientcert</literal> option with
2046+
<literal>cert</literal> authentication because <literal>cert</literal>
2047+
authentication is effectively <literal>trust</literal> authentication
2048+
with <literal>clientcert=verify-full</literal>.
20522049
</para>
20532050
</sect1>
20542051

0 commit comments

Comments
 (0)