mirror of
https://github.com/postgres/postgres.git
synced 2025-05-03 22:24:49 +03:00
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
This commit is contained in:
parent
d1c23d726d
commit
ef40ab77d5
@ -2042,13 +2042,10 @@ host ... radius radiusservers="server1,server2" radiussecrets="""secret one"",""
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In a <filename>pg_hba.conf</filename> record specifying certificate
|
||||
authentication, the authentication option <literal>clientcert</literal> is
|
||||
assumed to be <literal>verify-ca</literal> or <literal>verify-full</literal>,
|
||||
and it cannot be turned off since a client certificate is necessary for this
|
||||
method. What the <literal>cert</literal> method adds to the basic
|
||||
<literal>clientcert</literal> certificate validity test is a check that the
|
||||
<literal>cn</literal> attribute matches the database user name.
|
||||
It is redundant to use the <literal>clientcert</literal> option with
|
||||
<literal>cert</literal> authentication because <literal>cert</literal>
|
||||
authentication is effectively <literal>trust</literal> authentication
|
||||
with <literal>clientcert=verify-full</literal>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user