Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlc4p-003bdY-Ou for pgsql-docs@arkaria.postgresql.org; Wed, 27 Sep 2023 21:28:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlc4n-005yAk-Vb for pgsql-docs@arkaria.postgresql.org; Wed, 27 Sep 2023 21:28:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlc4n-005yAS-M1 for pgsql-docs@lists.postgresql.org; Wed, 27 Sep 2023 21:28:10 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlc4l-006zx5-Hu for pgsql-docs@lists.postgresql.org; Wed, 27 Sep 2023 21:28:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=WcuySLZ1chn8isjuJTVcZna3HwRCVYXYFyBNbHx0Y1I=; b=PIGisA632old8VSrgyFDwNuZaF L97Ufwj933L6C/DCRGaxYtMG2quf7MDYZEsdNV50RvvVAStqFlUT6cVEIvAABLPXjlfXaOqvBIt6L XWPqBfE7Kk5qgHcLeBJaQFWIuZLFcuQg2TGA4zwcieZI1FgW/g62rajGkJls3YDX7Qa2pWjfST0ID ip6fAi9Y6cIBW8NPlRXuFwtaHrM63DONR+o36OZH6Lcwysj8Zrtm+HnsDJN7MrC5o37fjzRktJHAQ +WOfq2I+a5IkblXKtWmLzfDatBfGw5T7k1x6QW2fS8VDLYVMNZpCWMRX3+Uhd86LvfcYQzjKPasgI qauEAiDg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qlc4i-006hf7-2N; Wed, 27 Sep 2023 17:28:04 -0400 Date: Wed, 27 Sep 2023 17:28:04 -0400 From: Bruce Momjian To: Peter Eisentraut Cc: Steve Atkins , pgsql-docs@lists.postgresql.org Subject: Re: Certificate authentication docs in multiple places Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="7QLhEK9BM9JPFyIS" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --7QLhEK9BM9JPFyIS Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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 https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you. --7QLhEK9BM9JPFyIS Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="cert.diff" diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 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"","" 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 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 cn (Common Name) --7QLhEK9BM9JPFyIS--