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 1vOUSf-009bNe-26 for pgadmin-support@arkaria.postgresql.org; Thu, 27 Nov 2025 05:22:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vOUSe-003Upr-0j for pgadmin-support@arkaria.postgresql.org; Thu, 27 Nov 2025 05:22:32 +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 1vOUSd-003Upi-33 for pgadmin-support@lists.postgresql.org; Thu, 27 Nov 2025 05:22:32 +0000 Received: from mail-yw1-x1130.google.com ([2607:f8b0:4864:20::1130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vOUSc-001j80-0T for pgadmin-support@lists.postgresql.org; Thu, 27 Nov 2025 05:22:32 +0000 Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-78a6c7ac3caso5363677b3.0 for ; Wed, 26 Nov 2025 21:22:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1764220947; x=1764825747; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tEM3KxIwIQcM2TorXikDRIWrQK+Rfz/youM2FqKT1b8=; b=SA4uoE9jmyQl1lsEVyfTVMiwgcG/pfIazd+46AhtHBPshv4qK0EUBWwMgw1QmwNraJ q8WWwzz9XJjiF9K3ibV8t4TjuPIB0y/OhskCAzYQh4UL3TEexSEh24lT8tIOGWc/RQzc epHxUnARQNg8lRMGSs74MStJb43eL6DrhRAj/MT+eGOaMN8p7hlppKavI5QlbgjBXTcg +AwOY20TgXM5OhLNDZjEgAxXknsS+vzzK8kK9buWmwMukWVL88Qc5/PDkcKho9I3iI6h 87RpyWltpMLBMpS7GwnQGeLY7o20YhC2vllunQNLy2YTxYHuSDNwQYJKr2gu+x5SAHEY 6MrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764220947; x=1764825747; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=tEM3KxIwIQcM2TorXikDRIWrQK+Rfz/youM2FqKT1b8=; b=GnEe2qI/DVrLjRdsYZ7wSTbSLrzP2NOLjNTKCRuJ+20Jyy0J+KGGx8CPyeQ9t0edhb Y8m7JScOdQdjdWRJlki+1iyVbtAjLUL3ekuzmtvnV/ihZIpO4AInzdUFcZE128Z23Ldc NdVqAHAPwkv24h1si/zR2dh/lxVehP1aEDywlUsU53izkvEl4+U0b+SI1wtwBfT3FdB8 t+c73JRj+383lXaZsBMjhlDqfK+WKYOrHEd8IZgfJzmHhSE6Cu93DY7vwh4w2ONq2AuZ tveBrtrcdY0Uwm8sDuHl7ksBxh5xL9L4dtMBwkBJgR6RWg0b9k0TMvrblAlqdpWFnvYW YsIA== X-Gm-Message-State: AOJu0YwQ8VYveA3Z9urOgom/wiRgsupH51yF6iNGnTNBCVH+h/vnDBPA y7/d6h3p6npVyvTUWFefKNy8q4btrTvJIws34UaiNz2DdZNOf0VI1OBn7XyLLy8b+mY7mAgs+vb pHEtGjdaLB/OkA123zuqhNlxOgQufYUU1Tbh9D9/1 X-Gm-Gg: ASbGncu3wcMXqTHcZN9DCteDxDgefXwmjXrAL1++0p5nVSGMsomTADTlFNsh2SLZNPU Dm3+YfhBuWdGJ7Hfc0SR+7llv5pCJxspVql0Iy6BAoXe1nCtW98j8orVzL/p0IIp49vkcLqOYhn X4wZxFHU/7jV+PfQufabBuo6J3GcOXRBOAedL6wjYPm6IDswBnpYtV348egyb7o/6sXPHA1FwIe UtCTOrQq8PgWozojGVECkjs54yoIJnFhFmRaQs03PYmsTQDnv2g4X6uYPTYvcvFaQ/rpCctqQ== X-Google-Smtp-Source: AGHT+IHJ7ezJtEBOqs9kOV5+sZXDlhBENSuK1UKKVCaym5I3M7XNRUfpSUr9Z+CnUaa3o5sK4aTeVBbkzAvuYq9uGmE= X-Received: by 2002:a05:690c:6c8a:b0:786:522f:f5b2 with SMTP id 00721157ae682-78a8b544869mr188236157b3.63.1764220947150; Wed, 26 Nov 2025 21:22:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Khushboo Vashi Date: Thu, 27 Nov 2025 10:52:16 +0530 X-Gm-Features: AWmQ_bmPApNfdsE-5qRPD3vaTV5xS-HBkoN31OhngMH0SCaw20Y5l3De4nNSmZQ Message-ID: Subject: Re: Kerberos authentication in pgAdmin4 server To: Haiko Sawatzky Cc: pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000dc49de06448cb2dd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000dc49de06448cb2dd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, While creating the server, have you checked the `Kerberos authentication ?' field? On Wed, Nov 26, 2025 at 8:57=E2=80=AFPM Haiko Sawatzky wrote: > Hello. > > I've been having seemingly the same issue as in the following thread: > https://www.postgresql.org/message-id/flat/CAFOhELe6QLp1ZJevkupqE9np%3DY7= GRWVd2WF_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 usin= g > 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 mome= nt > I try to connect to the Postgresql server: > pgadmin-1 | Error: connection failed: connection to server at > "", port 5432 failed: GSSAPI continuation error: No credentia= ls > 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 =3D /path/to/keytab". But as I said, when I configur= e > this in krb5.conf, the login into pgAdmin using Kerberos works. > --000000000000dc49de06448cb2dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

While creating the serve= r, have you checked the `Kerberos authentication ?' field?=C2=A0
<= br>
On Wed, Nov 26, 2025 at 8:57=E2=80=AFPM Haiko Sawatzky <= haikosaw69@gmail.com> wrote:=
Hello.

I've=C2=A0bee= n having seemingly the same issue as in the following thread: https://www.postgresql.org/message-id/flat/CAFOhELe6QLp1ZJe= vkupqE9np%3DY7GRWVd2WF_e4xbOM%2BxzO1W_A%40mail.gmail.com#0e78a396033b6d4d59= 22b1fa9b4ee880
I would like to see if someone can help me diagnose w= hat I'm doing wrong.

My environme= nt 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- Ubunt= u server VM
=C2=A0 * Our company = is using Microsoft Windows Active Directory

What I have worki= ng:
=C2=A0 * Logging into Postgresql directly with my Microsoft Active D= irectory user using Kerberos (from Windows & Linux)
=C2=A0 *=C2=A0Logging into pgAdmin web with my Micro= soft Active Directory user using Kerberos (currently only on Firefox on Win= dows)

What's=C2=A0currently not working for me is the Kerberos a= uthentication from within pgAdmin to the Postgresql server. The container l= ogs this the moment I try to connect to the Postgresql server:
pgadmin-1= =C2=A0| Error: connection failed: connection to server at "<ip-add= ress>", port 5432 failed: GSSAPI continuation error: No credentials= were supplied, or the credentials were unavailable or inaccessible: No Ker= beros 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/pgadm= in/krbccache/'
total 12
drwxr-xr-x =C2=A0 =C2=A02 pgadmin =C2=A0r= oot =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A04096 Nov 26 09:42 .
drwxrwxr-x =C2= =A0 =C2=A06 pgadmin =C2=A0root =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A04096 Nov 2= 6 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<= br>
I've=C2=A0tried, just to see if it would do a login:
=C2=A0 * Create an environment variable for = the whole container KRB5CCNAME as the abso= lute path to my Kerberos ticket in krbccache
=C2=A0 *=C2=A0copy the ticket in /var/lib/pgadmin/krbcca= che/ to /tmp/krb5cc_5050
The envi= ronment 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 a= t "<ip-address>", port 5432 failed: GSSAPI continuation err= or: Unspecified GSS failure.=C2=A0 Minor code may provide more information:= The ticket isn't for us
=
Another issue I've=C2=A0= already worked around: the documentation specifies to set an environment va= riable for "KRB_KTNAME"=C2=A0or set "KRB_KTNAME" in the= pgAdmin config,=C2=A0and that this should work instead of needing to confi= gure "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". But as = I said, when I configure this in krb5.conf, the login into pgAdmin using Ke= rberos works.
--000000000000dc49de06448cb2dd--