Just to explain my usecase, I just want every connection to try to GSSAPI authentication first (which is first rule in my pg_hba.conf), and if on failure it should attempt password authentication next (which is subsequent rule in pg_hba.conf)
Can you guide me to the right documentation or steps on how to add/update rules in pg_hba.conf for the possibility of gss-encrypted connections ? Because, whenever I establish successful connection with gssapi, I am getting below entry in log which shows authenticated=yes, encrypted=no,,
Anbazhagan M <gopi.anbumech@gmail.com> writes: > If psql v11 is behaving in a right way, what difference made psql v13 to > behave in a different way ? Was there any changes done between versions of > psql v11 and v13 ?
I told you already: I think the relevant difference is the addition of GSS (i.e. Kerberos or equivalent) support starting in v12. Both versions are behaving correctly according to their own feature sets. What is missing is that you need to update your pg_hba.conf to account for the possibility of GSS-encrypted connections.
From:
Andres Freund Date: Subject:
Re: Postgres connection growing memory usage over time! This right after the connections in the pool are closed and opened again.
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
✖
By continuing to browse this website, you agree to the use of cookies. Go to Privacy Policy.
