Re: Time to drop RADIUS support?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Michael Banck <mbanck(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Time to drop RADIUS support?
Date: 2026-01-25 01:02:44
Message-ID: 3497908.1769302964@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Great, it sounds like we have a plan. I think the wiki might be a
> good place for that documentation. The details are likely to change,
> and I wouldn't want to have to maintain that information in-tree, so I
> created some PAM how-to documentation at
> https://wiki.postgresql.org/wiki/RADIUS after testing on Debian and
> FreeBSD.

Ok ...

> We could point to that from the 19 release notes and in the
> deprecation notice added to the documentation for 14-18, calling it
> "community-maintained guidance on migration to supported
> configurations". Do we need to keep any trace of this in the 19 docs,
> and if so, where? A new tombstone section?

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.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florents Tselai 2026-01-25 01:15:39 Re: Add SQL/JSON ON MISMATCH clause to JSON_VALUE
Previous Message Tom Lane 2026-01-25 00:56:52 Re: ABI Compliance Checker GSoC Project