From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Steve Atkins <steve@blighty.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Certificate authentication docs in multiple places
Date: Wed, 27 Sep 2023 17:28:04 -0400
Message-ID: <ZRSeZH1Ytkm3Dj7v@momjian.us> (raw)
In-Reply-To: <a9be15ea-5853-d9bf-da7a-77d3a6b41df8@enterprisedb.com>
References: <B82E80DD-1452-4175-B19C-564FE46705BA@blighty.com>
<a9be15ea-5853-d9bf-da7a-77d3a6b41df8@enterprisedb.com>
On Tue, Mar 28, 2023 at 04:28:24PM +0200, Peter Eisentraut wrote:
> On 23.03.23 14:33, Steve Atkins wrote:
> > A couple of times recently I’ve been chatting with someone about using certificate authentication, and the docs they’ve found on it are the ones in section 21.12 (Client Authentication -> Certificate Authentication).
> >
> > But the useful documentation about how to set it up and use it is in section 19.9.3 (Secure TCP/IP Connections with SSL -> Using Client Certificates), where you’re less likely to find it while thinking about authentication.
> >
> > Should we add a link from the former to the latter?
>
> Sure, some cross-linking between those two sections seems sensible.
Attached is a patch which accomplishes this.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Attachments:
[text/x-diff] cert.diff (819B, ../ZRSeZH1Ytkm3Dj7v@momjian.us/2-cert.diff)
download | inline diff:diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgmlindex a72f80f033..82bfd25fd1 100644--- a/doc/src/sgml/client-auth.sgml+++ b/doc/src/sgml/client-auth.sgml@@ -2165,7 +2165,8 @@ host ... radius radiusservers="server1,server2" radiussecrets="""secret one"",""
<para>
This authentication method uses SSL client certificates to perform
- authentication. It is therefore only available for SSL connections.+ authentication. It is therefore only available for SSL connections;+ see <xref linkend="ssl-openssl-config"/> for SSL configuration instructions.
When using this authentication method, the server will require that
the client provide a valid, trusted certificate. No password prompt
will be sent to the client. The <literal>cn</literal> (Common Name)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, peter.eisentraut@enterprisedb.com, steve@blighty.com, pgsql-docs@lists.postgresql.org
Subject: Re: Certificate authentication docs in multiple places
In-Reply-To: <ZRSeZH1Ytkm3Dj7v@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox