From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Supporting fallback RADIUS server(s) |
Date: | 2015-08-20 10:57:31 |
Message-ID: | CABUevEwp=X1b00Lq-G13cC48bOMsWjkM-AO_GOcoFKLYWp7hWQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 20, 2015 at 12:55 PM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> On 8/20/15 12:53 PM, Magnus Hagander wrote:
>
>> We could change it to radius_servers and radius_ports, and deprecate but
>> keep accepting the old parameters for a release or two.
>>
>
> That's one option..
>
> To make it easy, we
>> make sure that both parameter names accepts the same format parameter, so
>> it's easy enough to just replace it once deprecated.
>>
>
> I'm not sure I understand what you mean by this.
I mean that you could write radius_server=foo or radius_servers=foo as well
as radius_server=foo,bar and radius_servers=foo,bar. As long as you don't
specify both radius_server and radius_servers, either one of them should
accept either one server or multiple servers.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2015-08-20 11:01:02 | Re: Supporting fallback RADIUS server(s) |
Previous Message | Marko Tiikkaja | 2015-08-20 10:55:40 | Re: Supporting fallback RADIUS server(s) |