Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lFNBG-0002Xf-KY for pgsql-bugs@arkaria.postgresql.org; Thu, 25 Feb 2021 20:24:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lFNBF-0008PM-FG for pgsql-bugs@arkaria.postgresql.org; Thu, 25 Feb 2021 20:24:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lFNBF-0008PF-9W for pgsql-bugs@lists.postgresql.org; Thu, 25 Feb 2021 20:24:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lFNBD-0004ZH-9S for pgsql-bugs@lists.postgresql.org; Thu, 25 Feb 2021 20:24:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 11PKO9Y1076902; Thu, 25 Feb 2021 15:24:09 -0500 From: Tom Lane To: Richard Crampton cc: Stephen Frost , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16897: gssenc request slow connection In-reply-to: References: <16897-2632c6541c9f8491@postgresql.org> <20210225174351.GU20766@tamriel.snowman.net> <73903.1614281357@sss.pgh.pa.us> Comments: In-reply-to Richard Crampton message dated "Thu, 25 Feb 2021 20:00:05 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <76900.1614284649.1@sss.pgh.pa.us> Date: Thu, 25 Feb 2021 15:24:09 -0500 Message-ID: <76901.1614284649@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Richard Crampton writes: > It's not enabled in my pg_hba.conf which I've attached... pg_hba.conf has zero to do with this. That's only an after-the-fact filter, besides which you haven't actually forbidden gssenc there. The important questions are (1) was the server built with --with-gssapi (probably, if your client was); (2) is a Kerberos ticket available to the server? If so, it will be willing to engage in a gss negotiation with the client. Given the data you've provided so far, it seems highly likely that (1) and (2) are true, since as Stephen says the case where gss is immediately rejected shouldn't take long. I think it's nearly certain that the problem is not really PG's, but reflects some sort of issue in your Kerberos/AD infrastructure. We don't have enough info to speculate about exactly what, though. regards, tom lane