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 1tVkkp-00B8md-1k for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 05:06:47 +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 1tVkko-00C2OF-DX for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 05:06:46 +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.94.2) (envelope-from ) id 1tVkko-00C2O7-0b for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 05:06:45 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVkkk-000fce-1p for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 05:06:45 +0000 Received: by mail-lf1-x142.google.com with SMTP id 2adb3069b0e04-5401e6efffcso553552e87.3 for ; Wed, 08 Jan 2025 21:06:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736399202; x=1737004002; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=BSkH1Bz3Djo9DYK4chehyp0C+kqxHDvid3g8ciYC8Sg=; b=MrumpcnEtaFEW3ffRxQg2SdtGrb7lhBs/0dhsQjECvePf97Xu/HVFHBEjCo6DGu87J D8KZuSSJq88fwgRTf3dDXZaSaKzrkQ/AYjEtWh3Q8ZJIEofAYv2ixHFG9lZJ56SSQFj6 sa4HYB1BinUjE7yt0mUCC1PvXZJVNcKMX3TDHxqrW2M0Lo3H5QJloYsxBarG3IAG9GnL cLDcB4+iv1etfRVxKqe972zShTToYdhVP3SyZxzT2P0opn5gUVFgVY3t8lX+Bzv+kMoj in1TUEdIT5aq8plcp8FKtXhOZrkjxX97j8e4CvNQl8HcORcSZVS2i5QMWtMSHRuTs6Ye 9jhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736399202; x=1737004002; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BSkH1Bz3Djo9DYK4chehyp0C+kqxHDvid3g8ciYC8Sg=; b=neTvHoej2fLew+qBUMdM2BSmgU1Bd9DJKEywCiLjAJjNmLCGlcudX5C0YX7MYFurcE cX+v8qTpR8qvUdeyxkXZL6FIGHBE3OTkdSsozXf2/xT7123RAXKjt5yeRfrv3yeqj9Z7 xysSEZ/4pIaojvblYJxwxH/XddvsU5mPRPBUTPey7SaI09IHxFr4qcRau8V/KfUCMdYW 2Hk8dG9YmtqoYc9Gn9obatf9vsCVPkLUO5VbdrfZIh8E+AYRKSI4rty9eNszkUAxH4iZ xDmkRffiIcQu+EpncuY639zGSbaeVn1+QRMPiV0dizgEle0gjn/SowD3pU0N0gxz6lP7 TW3A== X-Forwarded-Encrypted: i=1; AJvYcCXNyy3INpQqhEFTHk/3oGkNn4TW/fvTYJnzyu2UXS3CfmDDb4R3hDtSCxxVyXmrddRWmlRnLbCtiQ0I34hb@lists.postgresql.org X-Gm-Message-State: AOJu0Yw9+JYH+Ye7kzvcKpgqLyW4Qcq4G/CQ8RAdFUIc/rMd8thzilWP bUrJX9pSUSW3H+3kyB6+lhYF6pXtEsM+RKBDDy87lV4MlzGHsQ/XkHxZptVQUEv78+6KmLpQrXt RilW4/kz/idP5kznfA8W/4IX6tV4= X-Gm-Gg: ASbGncvQmIWXJ+p018GcpDWAtLP6SQV3ZhwKGn+b2IoLliNTFDnqNxyiF0/iC9TQUew 4Vj5mJulEFY3touRnv/cNd+SN/4eNjY0oAh1+XDfQbnP26I3IZZhMFnLduX4TVQTmjl0U/kQ= X-Google-Smtp-Source: AGHT+IG5f27dV5WDWbNbi1kyGEY30816DWh7Fl5tguxwx+VpBkcz4MtGABsheCoTcAaxvsUL/xwPBXOBRsIi0xNTjAE= X-Received: by 2002:a05:6512:b91:b0:542:297f:50c5 with SMTP id 2adb3069b0e04-542845b17camr1650636e87.1.1736399201658; Wed, 08 Jan 2025 21:06:41 -0800 (PST) MIME-Version: 1.0 From: vijay patil Date: Thu, 9 Jan 2025 10:36:31 +0530 X-Gm-Features: AbW1kvaydjogXvoUnB_11xtibLgD4Urpjr6rtIDo6pIl2VQuZPxSInrSO9IgnZY Message-ID: Subject: Issue with Password Authentication for Pgpool To: pgpool-general@pgpool.net, pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000009a70bc062b3ef1a6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009a70bc062b3ef1a6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Everyone, Need assistance on below requirements. My requirement is to prompt for a password when connecting through Pgpool (port 9999) and to avoid using the pool_password file. However, I=E2=80=99m currently getting the error related to the lack of an entry in the pool_passwd file. Could you please advise how I can achieve password authentication without using the pool_password file, while ensuring that Pgpool prompts for the password during connection? Here is the relevant configuration from my pool_hba.conf: host all all 10.125.0.90/32 trust # Node 1host all all 10.125.0.91/32 trust # Node 2#host all all 10.125.0.79/32 scram-sha-256 # Node 3host all all 0.0.0.0/0 scram-sha-256 # All nodes error :- [postgres@scrbtrheldbaas002 PG_DATA]$ psql -h 10.125.0.79 -U vkp -d postgres -p 9999 psql: error: connection to server at "10.125.0.79", port 9999 failed: FATAL: SCRAM authentication failed DETAIL: pool_passwd file does not contain an entry for "vkp" --0000000000009a70bc062b3ef1a6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello=C2=A0Everyone,

Need as= sistance=C2=A0on below=C2=A0requirements.=C2=A0

My= requirement is to prompt for a password when connecting through Pgpool (po= rt 9999) and to avoid using the pool_password file. However, I= =E2=80=99m currently getting the error related to the lack of an entry in t= he pool_passwd file.

Could you please advise how I can a= chieve password authentication without using the pool_password= file, while ensuring that Pgpool prompts for the password during connectio= n?


Here is the relevant configuration from my pool_h= ba.conf:

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         10.125.0.79/32       scram-sha-256    # Node 3
host    all         all         0.0.0=
.0/0            scram-sha-256    # All nodes
=

error :-
[postgres@scrbtrheldbaas002 PG_DATA]$ psql -h 10.125=
.0.79 -U vkp -d postgres -p 9999
psql: error: connection to server at "10.125.0.79", port 9999 fai=
led: FATAL:  SCRAM authentication failed
DETAIL:  pool_passwd file does not contain an entry for "vkp"


<= /div>
--0000000000009a70bc062b3ef1a6--