RE: Unable to get PostgreSQL 15 with Kerberos (GSS) working

Host file looks like:

127.0.0.1 localhost hostname hostname.mydomain.net
::1 localhost hostname hostname.mydomain.net
10.204.50.65 hostname hostname.mydomain.net

I also tried commenting out the ::1 line, but the issue moved to 127.0.0.1, commented that out and the issue moved to the IP. I really don’t get it. However, when I finally realised it was a localised issue (after days) I was able to move forward. No idea why it will not work on the server itself, but it is something I can live with.

Regards

Matt Dennison
From: Rob Sargent <robjsargent(at)gmail(dot)com>
Sent: Thursday, February 29, 2024 2:56 PM
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Unable to get PostgreSQL 15 with Kerberos (GSS) working

On 2/29/24 01:18, Matthew Dennison wrote:

Here's the results:

psql: error: connection to server at "hostname.mydomain.net" (::1), port 5432 failed: GSSAPI continuation error: Unspecified GSS failure. Minor code may provide more information: No Kerberos credentials available (default cache: KCM:)

If I run kinit and get Kerberos ticket ahead of running the command I then receive:

psql: error: connection to server at " hostname.mydomain.net " (::1), port 5432 failed: could not initiate GSSAPI security context: Unspecified GSS failure. Minor code may provide more information: Server not found in Kerberos database

connection to server at " hostname.mydomain.net " (::1), port 5432 failed: GSSAPI continuation error: Unspecified GSS failure. Minor code may provide more information: Server not found in Kerberos database

Should a FQDN resolve to ::1?