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 1qldee-003iw7-1S for pgsql-docs@arkaria.postgresql.org; Wed, 27 Sep 2023 23:09:16 +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 1qldeb-006LQC-S8 for pgsql-docs@arkaria.postgresql.org; Wed, 27 Sep 2023 23:09:14 +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 1qldeb-006LPn-JO for pgsql-docs@lists.postgresql.org; Wed, 27 Sep 2023 23:09:14 +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 1qldeX-0070eB-VZ for pgsql-docs@lists.postgresql.org; Wed, 27 Sep 2023 23:09:12 +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=pxDSpaxYRpWikU+akklIZveGB2GZ4BRIg934JspESeU=; b=pbtrC kxPq0pNYtx8Q7lmNezm1vUpy2GXd0Rj2X/EmMJ8kyySZ9oxyJSPaaKKskobBfCqfP2mI2OCh0ibp8 0flm9SuuGx+zYvVUtmzIgCwu6XMnwE5yWcOmuhOES8RbgjHuXZMt/DLA4dJEaXDgFAEXkH8mGg87W rMsNxLItaV9a18m6yidTwroI2I+4gZs8RfrQvLzNdo/72rkn0jMfKIwuncX1ugHT4qzuLvdwdoxh3 w+ehEDnypVAeInizneyjluRTGcRrzYu8rlOBB70oW9ekYe16F77En8pIHGS7FCG3Zbxqy5t4CzwbX kSkvsYLqWF+3qVbq9klGNo5lKn51w==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qldeQ-0071e0-15; Wed, 27 Sep 2023 19:09:02 -0400 Date: Wed, 27 Sep 2023 19:09:02 -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: multipart/mixed; boundary="Y5H3x42QKFE4NrpI" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Y5H3x42QKFE4NrpI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you. --Y5H3x42QKFE4NrpI Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="sspi.diff" diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml new file mode 100644 index a72f80f..fa53a0f *** a/doc/src/sgml/client-auth.sgml --- b/doc/src/sgml/client-auth.sgml *************** omicron bryanh *** 1505,1514 **** negotiate mode, which will use Kerberos when possible and automatically fall back to NTLM in other cases. ! SSPI authentication only works when both ! server and client are running Windows, ! or, on non-Windows platforms, when GSSAPI ! is available. --- 1505,1514 ---- negotiate mode, which will use Kerberos when possible and automatically fall back to NTLM in other cases. ! SSPI and GSSAPI ! interoperate as clients and servers. It is recommended to use ! SSPI on Windows clients and servers and ! GSSAPI on non-Windows platforms. --Y5H3x42QKFE4NrpI--