Re: Time to drop RADIUS support?
On 2026-Jan-23, Michael Banck wrote:
So you are saying we add a deprecation notice in the back branches and
drop it in V19? If this is a severe security issue then maybe we can
just remove it everywhere (ugh), or if not, I think it probably warrants
at least one release cycle of deprecation. Do we have a formal
deprecation timeline policy nowadays?
I don't think we do.
Would it work to add a WARNING (or something) to all back branches to
ask users to write here, so that we can confirm in the next few months
whether the protocol is completely unused or not? If we do find users,
then we could try to think of workarounds[*], but otherwise we'd just
remove it for pg19 (or pg20 at the latest) and not waste any more time
on it.
I don't think removing it entirely from all back branches is a good
idea, without first making sure that there are no users.
[*] or even just a way to document a migration to PAM-based Radius.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"I'm impressed how quickly you are fixing this obscure issue. I came from
MS SQL and it would be hard for me to put into words how much of a better job
you all are doing on [PostgreSQL]."
Steve Midgley, http://archives.postgresql.org/pgsql-sql/2008-08/msg00000.php
Import Notes
Reply to msg id not found: 20260123104322.GA17962@p46.dedyn.iolightning.p46.dedyn.io
On Sun, Jan 25, 2026 at 2:02 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
I think we don't want
https://www.postgresql.org/docs/current/auth-radius.html
to become 404, so I'd advocate keeping a short section with that
SGML ID that says we no longer support RADIUS directly and
gives a pointer to the wiki page. It probably doesn't belong
exactly where it is today in the TOC, though, but shoved off
in a corner somewhere.
TIL that there is an appendix for that very purpose. So, done.
Import Notes
Reply to msg id not found: 3497908.1769302964@sss.pgh.pa.us