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 1tVl9c-00BD6t-Ie for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 05:32:25 +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 1tVl9c-00CSX1-12 for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 05:32:23 +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 1tVl8a-00CNIc-UN for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 05:31:20 +0000 Received: from mail-ed1-x530.google.com ([2a00:1450:4864:20::530]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVl8Y-000eLF-0u for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 05:31:19 +0000 Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-5d122cf8dd1so718523a12.2 for ; Wed, 08 Jan 2025 21:31:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736400677; x=1737005477; 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=uo0vfWe5dcvJXJrf+4CZn5i4DHV5CW3UdDdRvPKS0PQ=; b=aeN+jU0y3FskwLRXUm/9G/eeJsvbyEKhnBl2dWIgLtKZl+WI3AUrxZ58X7NUPpFjVt XgCNyKVO0mrdilT4Hggp354MsPW0iFk+00cAMJHrWcBwZsyv60Oafzh6ODFYsafoZNGA 7GV2LEwf9saxJ/L0u0ScEX4Xcg+gvIt6LvLgI9iur2v7TUInmE63bw0xQC8GCuAtpgKe 0p5uo3qAfdYbysRlnnNtFuapUqsqsRHeX85NYAGZ8srQSmP4YYKxbVnUnwYz3FtEp0hH IGJI7hJKHZyWUl10SYW5LumdZL5dyH2bTWAsD9Gx2Ay5QnTqD9HhUfgPJ+2KPYO653Ez lsBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736400677; x=1737005477; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uo0vfWe5dcvJXJrf+4CZn5i4DHV5CW3UdDdRvPKS0PQ=; b=BF+2nVYyK6JNJBahDtyIxqormYDYdrDV01lYjEuN8uPMdI7bKle8ktRYy2hDdPu9+9 i8Vc1+YScMJVQNF/1MV0EFkhd21nt+tGs+CNlagldrvQ2qiCu3CZxcjG/6HWZ+RIuWeO ZkpLAFR8ftqxaRxP6aID5cS9YpbFq3fojuE9JdtB05Vghttpd3BMxTfg5H4MZzhREDUI Zi6kuPTvLgReJx3vhuv+qYz4x5dr00+YfYS+nLB/cN2HnJX7hrGPEe81JTefkN+uN6VU BZIhXvKWniPkF9eju3NovKhVauL8FHsNS8ZBZcFxEl8/kZS+WuPSWg1KW3IV0xJzHNaM sIIQ== X-Forwarded-Encrypted: i=1; AJvYcCUF+2A9PDkLxMTcFnHqlw1p24Ryg9BqZOXuv8RMw+7kSo17Fc7G9iAX+bPGBobAiYshrzYrOL+D8WlHXBOa@lists.postgresql.org X-Gm-Message-State: AOJu0YzhUIA3a9OyrtniaFlzQOJ7S57RUk9QVOr4wjCkSxyilMDnir6Y GR8VgAuT77C5kMWlVnZOdv08B1IL+dj3OKe2tqx+bjhIwDUHd97/jh77/9u07lkh4qfaZfcI9T2 yZuRPMhirmJ2BcKS6HHU3sK3equQ= X-Gm-Gg: ASbGnctee3vkWjatKw/G1s+zc9zqtMjRnrwqhrx21gkKK/8fCr3agXQf2nBMCW/d1Sa jVFY7fptpmB2NT1KU6vwuLYiqkiRfPL0uIvCbLjqznJgZubbQ77s0a6zJSL9mt/oyx9SDYOk= X-Google-Smtp-Source: AGHT+IGehXy0ncxPvOGGPUG0v1YXa3YhTVGTvH25evJ6qRTthNRtkw7YXqWKYrOg2dF8jB4LtPP5uK9X32VR8yNpSVM= X-Received: by 2002:a05:6402:4306:b0:5d0:c9e6:309d with SMTP id 4fb4d7f45d1cf-5d972dfe6a0mr4589022a12.1.1736400676693; Wed, 08 Jan 2025 21:31:16 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: vijay patil Date: Thu, 9 Jan 2025 11:01:00 +0530 X-Gm-Features: AbW1kvYErOITKSdInkI8LzuJjhL5QajBRmqrcxmZCw-nO7HD7KzZEO5nV8TqP4Q Message-ID: Subject: Re: Issue with Password Authentication for Pgpool To: "David G. Johnston" Cc: "pgpool-general@pgpool.net" , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000085b213062b3f498f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000085b213062b3f498f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks David, I tested the configuration by setting allow_clear_text_frontend_auth =3D on and disabling the pool_hba. I made the corresponding entry in the pg_hba.conf file. However, while connecting through the database port (5432), it prompts for the password, but when connecting through Pgpool (port 9999), it does not ask for a password. Here is the content of pg_hba.conf: bash Copy code # TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connections onlylocal all all trust# IPv4 local connections: host all all 127.0.0.1/32 trust# IPv6 local connections: host all all ::1/128 trust# Allow replication connections from localhost, by a user with the# replication privilege.local replication all trust host replication all 127.0.0.1/32 trust host replication all ::1/128 trust host repmgr repmgr 127.0.0.1/32 trust host repmgr repmgr 10.125.0.90/32 trust # Primary host replication repmgr 10.125.0.90/32 trust host repmgr repmgr 10.125.0.91/32 trust # Standby host replication repmgr 10.125.0.91/32 trust host all all 10.125.0.90/32 trust # Nod= e 1 host all all 10.125.0.91/32 trust # Node 2#host all all 0.0.0.0/26 trust host all all 10.125.0.79/32 scram-sha-256 host all all 0.0.0.0/0 scram-sha-256 When I connect via the database port (5432), it prompts for the password as expected: [postgres@scrbtrheldbaas002 ~]$ psql -h 10.125.0.79 -U vkp -d postgres -p 5= 432 Password for user vkp: psql (15.3) Type "help" for help. postgres=3D> postgres=3D> postgres=3D> exit However, when connecting through Pgpool (port 9999), it does not prompt for the password: [postgres@scrbtrheldbaas002 ~]$ psql -h 10.125.0.79 -U vkp -d postgres -p 9= 999 psql (15.3) Type "help" for help. postgres=3D> This behavior might be related to how Pgpool handles authentication. Let me know if you need further investigation or configuration changes! Thanks Vijay On Thu, Jan 9, 2025 at 10:47=E2=80=AFAM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Wednesday, January 8, 2025, vijay patil > wrote: > >> Could you please advise how I can achieve password authentication withou= t >> using the pool_password file, while ensuring that Pgpool prompts for the >> password during connection? >> > > > https://www.pgpool.net/docs/latest/en/html/runtime-config-connection.html= #GUC-ALLOW-CLEAR-TEXT-FRONTEND-AUTH > > David J. > --00000000000085b213062b3f498f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks=C2=A0David,

= I tested the configuration by setting allow_clear_text_frontend_auth = =3D on and disabling the pool_hba. I made the corresponding entry in= the pg_hba.conf file. However, while connecting through the d= atabase port (5432), it prompts for the password, but when connecting throu= gh Pgpool (port 9999), it does not ask for a password.

Here is the co= ntent of pg_hba.conf:

bash
# TYP=
E  DATABASE        USER            ADDRESS                 METHOD
# "local" is for Unix domain s=
ocket connections only
local   all             all     =
                                trust
# IPv4 local connections:
host    all             all             127=
.0.0.1/32            trust
# IPv6 local connections:
host    all             all             ::1/128                 trust
# Allow replication connections from loc=
alhost, by a user with the
# replication privilege.
local   replication     all     =
                                trust
host    replication     all             127=
.0.0.1/32            trust
host    replication     all             ::1/128                 trust
host    repmgr          repmgr      127.0.0=
.1/32            trust
host    repmgr          repmgr      10.12=
5.0.90/32             trust           # Primary
host    replication     repmgr      10.12=
5.0.90/32             trust
host    repmgr          repmgr      10.12=
5.0.91/32             trust           # Standby
host    replication     repmgr      10.12=
5.0.91/32             trust
host    all         all         10.125.0.=
90/32       trust            # Node =
1
host    all         all         10.125.0.=
91/32       trust            # Node =
2
#host    all         all         0.0.0.0/26          trust
host    all         all         10.125.0.=
79/32           scram-sha-256
host    all         all         0.0.0.0/0 =
          scram-sha-256

When I connect via the database port (5432), it= prompts for the password as expected:

[postgres@scrbtrheldbaas002 ~]$ psql -h 10.125.0.79 =
-U vkp -d postgres -p 5432
Password for user vkp:
psql (15.3)
Type "help" for help=
.

postgres=3D>
postgres=3D>
postgres=3D> exit

However, when connecting through Pgpool (port 9= 999), it does not prompt for the password:

[postgres@scrbtrheldbaas002 ~]$ psql -h 10.125.0.79 -U vkp -d post=
gres -p 9999
psql (15.3)
Type "help" for help=
.

postgres=3D>

This behavior might be related to how Pgpool ha= ndles authentication. Let me know if you need further investigation or conf= iguration changes!

Thanks

Vijay


On Thu, Jan 9, 2025 at 10:47=E2=80=AFAM David G. Johnston <david.g.johnston@gmail.com> w= rote:
On Wednesd= ay, January 8, 2025, vijay patil <vijay.postgres@gmail.com> wrote:
Could you please advise= how I can achieve password authentication without using the pool_pas= sword file, while ensuring that Pgpool prompts for the password duri= ng connection?