Re: Require SSL connection to postgres for oauth

> On 18 Jun 2026, at 06:54, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:

> I added another patch which is only a documentation improvement,
> that's the new 0001. The documentation is very clear about "password"
> being insecure over plaintext connections, but there's no such mention
> for oauth.

I cam absolutely get behind an improvement of the docs for master through 18
for this, ideally in time for the next minors. The attached .txt
(intentionally not a .diff or .patch since I didn't re-send your full patchset)
massages your 0001 to make it more consistent with the rest of the
documentation.

> 0002 and 0003 are the previous patches unchanged.

I am intrerested in raising the security model for postgres connections, but as
mentioned here and elsewhere it does require careful study of common container
environments like Kubernetes which may be impacted. For v19 I don't see it as
a realistic change (and I think it was too late even when initially raised,
even though it was a lot earlier in the cycle than now), but hopefully we can
raise the bar in v20.

--
Daniel Gustafsson