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.96) (envelope-from ) id 1vOHTo-000csH-2X for pgadmin-support@arkaria.postgresql.org; Wed, 26 Nov 2025 15:30:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vOHTn-00HT81-1Q for pgadmin-support@arkaria.postgresql.org; Wed, 26 Nov 2025 15:30:51 +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.96) (envelope-from ) id 1vOGmH-00HAiU-1T for pgadmin-support@lists.postgresql.org; Wed, 26 Nov 2025 14:45:53 +0000 Received: from mail-il1-x132.google.com ([2607:f8b0:4864:20::132]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vOGmE-001cd3-1s for pgadmin-support@lists.postgresql.org; Wed, 26 Nov 2025 14:45:53 +0000 Received: by mail-il1-x132.google.com with SMTP id e9e14a558f8ab-4330d2ea04eso27306565ab.3 for ; Wed, 26 Nov 2025 06:45:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764168348; x=1764773148; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=6AiMQeUJvlQirQmSXiPR6DszIiomJXoaFy7akfE19aI=; b=ecdHfa+0ahq6CnNCRfUKFxcUFeiOB0ZiTOgiMYFq3vx3q1ouheVrn5BmrtvvGB4qvY M5oll8wG1QPLWHX+7r08xllvoezphxOhg/sCDyjJkbcxBNwZdUfIUEFKlNM7e5+pN+rc CXHzf7NiybjgYvOZexfNQ37sK/CMTngN9uAJqAA4mjQRKXFgSs0hHVnohjvSogXaaKK6 qzgR5s20m3xZOghHX1rYwZtly9wCgbkx+H94Jth/IOBhnDGs1orOXoXXJOJrLRGOwFCU pW7nrYxebEXV3Ev1GkC6x9e+BslmBhQMfkKmCIGqah9ugiVQ+7hskQj4FNgypmYJp6YC ddIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764168348; x=1764773148; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6AiMQeUJvlQirQmSXiPR6DszIiomJXoaFy7akfE19aI=; b=JrHh3r4Y8HjVhGrNq83zwfkbXrlRCWmJ/MZ3hD7ntjUlPMQfzFQdq0ofYwn/78wfcF lOXrXW0P102/yigmH5KWQMtenIdIMDKiLrHYRe99CgRziuWOQC4vDhPoBuMesq6rMh36 0HXOWafHA26jboIDz6fqF8LGiibzQ2GWjruCP32TK1OzPMBQfQHEi//FwDLf5RIMtgvI rF+JmDbXuPpDmcnGbAPM0levGu6zvlceXdr3T3TmZ5INaUoik8fDZinBFVIAcfFegVNh HvgiMfQy2/xg9H6evDSvICwSHVcwfnuaq2muV+RTu1OwsWUXNuZSaPk7EKWdjglfaZ7s 4oMA== X-Gm-Message-State: AOJu0Yynnvpat9uh/j7TP5pOhvj51/y8rvU+pGEfpECK1u7i+8YAViPE B/cNIHG18Ctnz8f7WamxzEAPm99TYd1/riwVHDU4D/K/d3MqKO1nWPmCQ8W+H5nB/ylt/0UMFcJ HgkWuqBgsqC69kqW69rt22A3Z1uaCtiWLXdjh X-Gm-Gg: ASbGncvQ0T2YC6hiK4q5Hhzv1B+XZIRzpZIg4Ce8JEaXl+W+xagWRzZwF2Vdl49pn2F II47Ah1H3t8O6pIAltiEkyU2S/WJdBAXdusqmJVlc32M9VkmJ8w6GC5rt9u2LhEJKtrvzwcP1ae zJl+sjErwY9IPvNL3N4oFRzzx0/K9SGEPLyNjuUnZet+xXsWqdjoBzC0Cw81AK3wccg+o6r3gGj 3jOzm02PQS9GYJ54zBADgWBuhm4gNcM/qEIw5/NIX31dlMDoNYC971lJRcf9Nz88sRYwynaOfLb W3oD+V4= X-Google-Smtp-Source: AGHT+IF78bXtsAawEfnYmoYAkWScCwxe/IHPmuRCA/8qUklM/IfqsL3NXAcdo9u3OSgcmLLLhzD8aT12p76r2Wniba8= X-Received: by 2002:a05:6e02:1a27:b0:433:551d:5f2c with SMTP id e9e14a558f8ab-435dd117e99mr80856595ab.29.1764168347914; Wed, 26 Nov 2025 06:45:47 -0800 (PST) MIME-Version: 1.0 From: Haiko Sawatzky Date: Wed, 26 Nov 2025 11:45:36 -0300 X-Gm-Features: AWmQ_blS6zogIxid8MIIB-XcvsgKyQUxDZl9-0bZJjPfKBqDz9-GSjhfUGYthk0 Message-ID: Subject: Kerberos authentication in pgAdmin4 server To: pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000b39e320644807380" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b39e320644807380 Content-Type: text/plain; charset="UTF-8" Hello. I've been having seemingly the same issue as in the following thread: https://www.postgresql.org/message-id/flat/CAFOhELe6QLp1ZJevkupqE9np%3DY7GRWVd2WF_e4xbOM%2BxzO1W_A%40mail.gmail.com#0e78a396033b6d4d5922b1fa9b4ee880 I would like to see if someone can help me diagnose what I'm doing wrong. My environment is: * pgAdmin4 server version 9.10, running in a Docker container (dpage/pgadmin4:9.10) - Ubuntu server VM * Postgresql server configured for Kerberos authentication - Ubuntu server VM * Our company is using Microsoft Windows Active Directory What I have working: * Logging into Postgresql directly with my Microsoft Active Directory user using Kerberos (from Windows & Linux) * Logging into pgAdmin web with my Microsoft Active Directory user using Kerberos (currently only on Firefox on Windows) What's currently not working for me is the Kerberos authentication from within pgAdmin to the Postgresql server. The container logs this the moment I try to connect to the Postgresql server: pgadmin-1 | Error: connection failed: connection to server at "", port 5432 failed: GSSAPI continuation error: No credentials were supplied, or the credentials were unavailable or inaccessible: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_5050) I do however find a ticket for my Kerberos session in the cache directory: docker exec -ti pgadmin-test-pgadmin-1 bash -c 'ls -la /var/lib/pgadmin/krbccache/' total 12 drwxr-xr-x 2 pgadmin root 4096 Nov 26 09:42 . drwxrwxr-x 6 pgadmin root 4096 Nov 26 09:42 .. -rw------- 1 pgadmin root 1533 Nov 26 09:42 pgadmin_cache_testuser@AD.DOMAIN.LAB I've tried, just to see if it would do a login: * Create an environment variable for the whole container KRB5CCNAME as the absolute path to my Kerberos ticket in krbccache * copy the ticket in /var/lib/pgadmin/krbccache/ to /tmp/krb5cc_5050 The environment variable had no affect, but copying the ticket to /tmp/krb5cc_5050 changed the error that I got to: pgadmin-1 | Error: connection failed: connection to server at "", port 5432 failed: connection to server at "", port 5432 failed: GSSAPI continuation error: Unspecified GSS failure. Minor code may provide more information: The ticket isn't for us Another issue I've already worked around: the documentation specifies to set an environment variable for "KRB_KTNAME" or set "KRB_KTNAME" in the pgAdmin config, and that this should work instead of needing to configure "default_keytab_name" in krb5.conf. But this has not worked for me at all, I can't go without explicitly creating a krb5.conf file that specifies "default_keytab_name = /path/to/keytab". But as I said, when I configure this in krb5.conf, the login into pgAdmin using Kerberos works. --000000000000b39e320644807380 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello.

I&= #39;ve=C2=A0been having seemingly the same issue as in the following thread= : https://www.postgresql.org/message-id/flat/C= AFOhELe6QLp1ZJevkupqE9np%3DY7GRWVd2WF_e4xbOM%2BxzO1W_A%40mail.gmail.com#0e7= 8a396033b6d4d5922b1fa9b4ee880
I would like to see if someone can hel= p me diagnose what I'm doing wrong.

My environment is:
=C2=A0 * pgAdmin4= server version 9.10, running in a Docker container (dpage/pgadmin4:9.10) -= Ubuntu=C2=A0server=C2=A0VM
=C2=A0 * Postgresql server configured for Kerberos authentication= =C2=A0- Ubuntu server VM
=C2=A0 *= Our company is using Microsoft Windows Active Directory
<= font face=3D"monospace">
What= I have working:
=C2=A0 * Logging into Postgresql directly with my Micro= soft Active Directory user using Kerberos (from Windows & Linux)
=
=C2=A0 *=C2=A0Logging into pgAdmin web = with my Microsoft Active Directory user using Kerberos (currently only on F= irefox on Windows)

What's=C2=A0currently not working for me is t= he Kerberos authentication from within pgAdmin to the Postgresql server. Th= e container logs this the moment I try to connect to the Postgresql server:=
pgadmin-1 =C2=A0| Error: connection failed: connection to server at &qu= ot;<ip-address>", port 5432 failed: GSSAPI continuation error: N= o credentials were supplied, or the credentials were unavailable or inacces= sible: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_5= 050)

I do however find a ticket for my Kerberos session in the cache= directory:
docker exec -ti pgadmin-test-pgadmin-1 bash -c 'ls -la /= var/lib/pgadmin/krbccache/'
total 12
drwxr-xr-x =C2=A0 =C2=A02 pg= admin =C2=A0root =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A04096 Nov 26 09:42 .
d= rwxrwxr-x =C2=A0 =C2=A06 pgadmin =C2=A0root =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A04096 Nov 26 09:42 ..
-rw------- =C2=A0 =C2=A01 pgadmin =C2=A0root =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01533 Nov 26 09:42 pgadmin_cache_testuser@AD.= DOMAIN.LAB

I've=C2=A0tried, just to see if it would do a login:<= /font>
=C2=A0 * Create an environment va= riable for the whole container KRB5CCNAME = as the absolute path to my Kerberos ticket in krbccache
=
=C2=A0 *=C2=A0copy the ticket in /var/lib/pga= dmin/krbccache/ to /tmp/krb5cc_5050
The environment variable had no affect, but copying the ticket to=C2=A0/= tmp/krb5cc_5050 changed the=C2=A0error that I got to:
pgadmin-1 =C2=A0| Error: connection failed: connection= to server at "<ip-address>", port 5432 failed: connection = to server at "<ip-address>", port 5432 failed: GSSAPI conti= nuation error: Unspecified GSS failure.=C2=A0 Minor code may provide more i= nformation: The ticket isn't for us

Another issue I&#= 39;ve=C2=A0already worked around: the documentation specifies to set an env= ironment variable for "KRB_KTNAME"=C2=A0or set "KRB_KTNAME&q= uot; in the pgAdmin config,=C2=A0and that this should work instead of needi= ng to configure "default_keytab_name" in krb5.conf. But this has = not worked for me at all, I can't go without explicitly creating a krb5= .conf file that specifies "default_keytab_name =3D /path/to/keytab&quo= t;. But as I said, when I configure this in krb5.conf, the login into pgAdm= in using Kerberos works.
--000000000000b39e320644807380--