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 1qqJhd-009FYy-3w for pgsql-docs@arkaria.postgresql.org; Tue, 10 Oct 2023 20:51:41 +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 1qqJha-00AYpo-VC for pgsql-docs@arkaria.postgresql.org; Tue, 10 Oct 2023 20:51:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qqJha-00AYpg-N9 for pgsql-docs@lists.postgresql.org; Tue, 10 Oct 2023 20:51:39 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qqJhX-001Llm-1o for pgsql-docs@lists.postgresql.org; Tue, 10 Oct 2023 20:51:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=nqJpuunPAh9RJPK/T4froogmZEAFfSxyXDQ7P22g+7c=; b=4B6DW 5wqboxucUXHsnhO6OPWQEkjMOtVnWO6my55PVvPS8InovXoPsJIlQk3htXttiYNjGGwDIyeLNTy2D zi1lqZOFqV5/E5rou2CQTPnPcoJpAXx2iEriuvP3ZLqBzc1T/9VNewHzhOyc7QNGQeh1KV+m7dhC9 rpS1xDyXaN3kSqPD66GdG1Rj6rkWv+n9/IFx0cuzMvw5D3VF6851AjcjtvdZzqtc3dY+M1QUyDGAx BETu+B0aONYSOquone0utRkQeqRPFvZwuktwMMk/ITJQTEtozB3PRtJr7TJIMZcIz560E1m5HXdF0 vyLpIgooCg/9+U7IX9YZRPCB/nMAQ==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qqJhP-000hdR-2J; Tue, 10 Oct 2023 16:51:27 -0400 Date: Tue, 10 Oct 2023 16:51:27 -0400 From: Bruce Momjian To: Stephen Frost Cc: tpo_deb@sourcepole.ch, pgsql-docs@lists.postgresql.org Subject: Re: Make SSPI documentation clearer Message-ID: References: <167846222574.1803490.15815104179136215862@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Sep 28, 2023 at 09:55:43AM -0400, Bruce Momjian wrote: > On Wed, Sep 27, 2023 at 07:09:02PM -0400, Bruce Momjian wrote: > > On Sun, Mar 12, 2023 at 08:36:53PM -0400, Stephen Frost wrote: > > > > When the server is on a non-Windows platform then the server must use GSSAPI > > > > if it wants to authenticate the client either via Kerberos or via Active > > > > Directory. A client on a Windows platform that connects to a non-Windows > > > > Postgresql server can either use SSPI (strongly encouraged) or GSS (much > > > > more difficult to set up) if it wants to authenticate via Kerberos or Active > > > > Directory. A client from a non-Windows platform must use GSS if it wants to > > > > authenticate via Kerberos or Active Directory." > > > > > > Rather than work in negative, I feel like it might make more sense to > > > work in positives? That is, perhaps this instead: > > > > > > On Windows platforms, SSPI is the default and most commonly used > > > mechanism. Note that an SSPI client can authenticate to a server which > > > is using either SSPI or GSSAPI, and a GSSAPI client can authenticate to > > > a server which is using either SSPI or GSSAPI. Generally speaking, > > > clients and servers on Windows are recommended to use SSPI while clients > > > and servers on Unix (non-Windows) platforms use GSSAPI. > > > > I developed the attached patch. > > My first attempt was too terse, so here is a more detailed version, > attached. Patch applied back to PG 11. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.