Thanks for the clarification Tom Lane.
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,,
2023-01-10 02:23:46.835 EST [3813278] LOG: 00000: connection authorized: user=app_kdc_test_fid database=postgres application_name=psql SSL enabled (protocol=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384, bits=256, compression=off) GSS (authenticated=yes, encrypted=no, principal=kdc_test_fid/
x.x.x@WLAB.NET)
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.
regards, tom lane
--