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 1tVleq-00BHGL-QF for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 06:04:41 +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 1tVleq-00Cujf-55 for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 06:04:39 +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 1tVlep-00CuiR-Nq for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 06:04:39 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVlem-000gAY-1Z for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 06:04:39 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-5d9882a936eso750914a12.3 for ; Wed, 08 Jan 2025 22:04:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736402675; x=1737007475; 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=gEIeLfpCcbhj31w+J/siXBBt/t6bRUI17k7aRKliW5Q=; b=CkPWhHyFIIKgGH8TYXb0qq06d8dNb7vsf2GcMLGNLdb52uKACp5bTPI+0SWpSqOTvD VG+068lgWJRhaH30CSneCiy/RzO2f3phttcFa4b647ReKSvWofVQnPXh2qjCWBnF3wtr toTvLQfEGyIv+cPpqaHUY4AJrWGUSwdr1ALOLC+f/u/O1JSZRtIAzZQw5XzIpOUXtcDy m3DO6XJ4QYv39xYKJOykaZNzIV0gpnAj97NsF1jFlRR2v02HVou9s78ALTwdyIo5zrn8 993eyAt8Joh3D5+r2G6qCT/dBnlmSDzegUzsoD9c4J4Y0R+OfKuhtuoMSWfckQGmJ24f KpPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736402675; x=1737007475; 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=gEIeLfpCcbhj31w+J/siXBBt/t6bRUI17k7aRKliW5Q=; b=LcXzv8q3DOKjxgCj8zKRM5cfihiRCTFlNmLXwRX6tNoSDKvm+Fczf2G9ckrOogSHvk Rn/ol1u6Dper5mUgkIGs8BrkO0N8nDD2CCj6VjiBKPIpggNtfd6E22w68QXtYPI/tOdN 1YESnjaoZKd5w/7QoZgomFKvTHwHeLnWnvk9NQ/ZhSBeHbVEl4GvncWTxaQEddGfVW40 Wr/DHYVwHrx9BQm3FoBE3HJ+xjLJCfvWe6J2BV7omKHEgT2SJSKxdgvhq5S5NzBx4DOY HBJGGWoSBj318LouPQm9HpMNCqmDD8wbkPWwv+vA/GXJz/dLw/zd/y+wiKPN+tBtezs0 qKUQ== X-Gm-Message-State: AOJu0Ywj1LbznOEZrUejzjF5Aart1i6wAbcaAkdSedZHgpdGQ9c3V6+1 wJYX0tyV8KqfVaTgdqWdI32I/XW8wBGiVnZ+NpUpNwB10yZ9OMkYxnfzxpvn96u8ZBHN6+h689I ooq2Bv8CHcL13Q8wsX9gGhWmccd/Q98WH X-Gm-Gg: ASbGncukWRcW8U7DGmPTGlnHXwSBaqQOKaX4vdjerx5yZgJQ7Q5uRTSxMKNMgQ+3hjb OgYUdYsuBMmJuzgtzuX5pWyWBuVbx2IZUMqB97bXSYnDCp3GSmm6hjSWmbjz42EO8ZvvBoTw= X-Google-Smtp-Source: AGHT+IH13X+2X+HDFMAKCa8DFpX5ZHAVg/PLXk7sQwTH0wU42rGYFjO/IDQ1YBIbNX3XQ6b12KIVizZTDOFa9dypccM= X-Received: by 2002:a05:6402:1d50:b0:5d3:f141:ccf6 with SMTP id 4fb4d7f45d1cf-5d972e6f4a6mr4820040a12.32.1736402675317; Wed, 08 Jan 2025 22:04:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: vijay patil Date: Thu, 9 Jan 2025 11:34:23 +0530 X-Gm-Features: AbW1kva5pvY_kuX4Na0aisRH_KqZ05L4_2If5oG9ua4UJsP8QuKkAwux4SQg7oI Message-ID: Subject: Re: Issue with Password Authentication for Pgpool To: "David G. Johnston" Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000a6428a062b3fc0db" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a6428a062b3fc0db Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If we plan to use pool_hba.conf, then we must use the pool_passwd file to maintain passwords for all database users. This approach requires that every time a new user is created, their password is added to the pool_passw= d file. The challenge with this method is that it becomes difficult to maintain, as we need to manually update the pool_passwd file for every user creation or password change. Additionally, after updating the pool_passwd file, Pgpool needs to be restarted for the changes to take effect. Thanks Vijay On Thu, Jan 9, 2025 at 11:14=E2=80=AFAM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Wednesday, January 8, 2025, vijay patil > wrote: > >> This behavior might be related to how Pgpool handles authentication. >> > > Having never used pgpool I very well could be wrong but from what I can > gather what you want to do is simply not possible within the current desi= gn > of pgpool. Namely you have multiple nodes so cannot rely on raw mode but > raw mode is required for the kind of pass-through auth you are trying. > Instead you require pool_hba.conf which itself requires the password file= . > > David J. > > --000000000000a6428a062b3fc0db Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If we plan to use pool_hba.conf, then we must use the pool_passwd file to maintain passwor= ds for all database users. This approach requires that every time a new use= r is created, their password is added to the pool_passwd file.= The challenge with this method is that it becomes difficult to maintain, a= s we need to manually update the pool_passwd file for every us= er creation or password change. Additionally, after updating the pool= _passwd file, Pgpool needs to be restarted for the changes to take e= ffect.

Thanks
Vijay

On Thu, Jan 9, 2025 at 11:14=E2=80=AFAM David G. Johnsto= n <david.g.johnston@gmail.= com> wrote:
On Wednesday, January 8, 2025, vijay patil <vijay.postgres@gmail.com> wrote= :

This behavior might be related to how Pgpool handles authe= ntication.


Having never use= d pgpool I very well could be wrong but from what I can gather what you wan= t to do is simply not possible within the current design of pgpool.=C2=A0 N= amely you have multiple nodes so cannot rely on raw mode but raw mode is re= quired for the kind of pass-through auth you are trying.=C2=A0 Instead you = require pool_hba.conf which itself requires the password file.
David J.

--000000000000a6428a062b3fc0db--