[pgpool-general: 8923] Re: Mapping frontend username+password with different backend username+password

Bo Peng pengbo at sraoss.co.jp
Tue Aug 29 10:42:47 JST 2023


Hi,

Thank you.

Currently, pgpool doesn't support this feature.
I will ask other developer who implemented the code of authentication.

Usama,

Do you have any idea about this mapping feature?

On Fri, 25 Aug 2023 19:14:01 +0200 (CEST)
Patrick Peters <p.k.f.peters at xs4all.nl> wrote:

> I am currently using PGpool-II v4.0.2 and got it working as a proxy for
> legacy software that need to connect to a new PostgreSQL server that
> is located in a Kubernetes cluster.
>  
> The only problem i got is mapping between a frontend authentication and a
> backend authentication. I can only get the pool_passwd entry to check the
> frontend and also pass that authentication on to the backend.
>  
> I looked at the code of v4.0.2 and also v4.4.4 and found out there was also
> some work done on this by using a backend set of credentials on the same
> line in the pool_passwd file. As i understand this is what is expected in code:
>  
> [frontend username]:[frontend password]:[backend username]:[backend password]
>  
> Which would be great for my application as i would like to have the frontend
> username 'postgres' to be mapped to another backend user called: 'appsuser'
> I tried this but it did not work; pgpool still tries to authenticate with the frontend
> username to the backend.
>  
> I looked through the code some more but i am beginning to think this feature
> is not yet fully implemented. I could not find a place in the code where the backend
> username is checked and if present used to authenticate with the backend.
>  
> Does anyone know if the mapping feature is available and if so please tell
> me how i can configure this.

-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS LLC
TEL: 03-5979-2701 FAX: 03-5979-2702
URL: https://www.sraoss.co.jp/



More information about the pgpool-general mailing list