Re: Multiple LDAP Servers for ldap Authentication

From: Christopher Browne <cbbrowne(at)gmail(dot)com>
To: "Kumar, Virendra" <Virendra(dot)Kumar(at)guycarp(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Multiple LDAP Servers for ldap Authentication
Date: 2018-12-20 23:16:18
Message-ID: CAFNqd5U_VYMi0V6CTwB7gNX0YSXJE+a1gNgYCB31fDH65T3=VA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 20 Dec 2018 at 16:17, Kumar, Virendra
<Virendra(dot)Kumar(at)guycarp(dot)com> wrote:
>
> I figured it out, this is how it works:
> --
> host all all 0.0.0.0/0 ldap ldapserver=server1.com ldapserver=server2.com ldapprefix=PROD01\
>
> So documentation need some update.

Looking at the docs (doc/src/sgml/client-auth.sgml), it appears to be
correct, though it is somewhat ambiguous in that I'd expect
"ldapserver=server1.com server2.com" to be OK rather than needing
"ldapserver=server1.com ldapserver2.com" instead. I'm not certain of
a way to explain this better.

<varlistentry>
<term><literal>ldapserver</literal></term>
<listitem>
<para>
Names or IP addresses of LDAP servers to connect to. Multiple
servers may be specified, separated by spaces.
</para>
</listitem>
</varlistentry>

Perhaps the attached?

--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

Attachment Content-Type Size
fix.diff text/x-patch 575 bytes

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-12-21 00:56:35 Re: Change from 9.6 to 11?
Previous Message Ian Lawrence Barwick 2018-12-20 22:45:56 Re: Wals not recycling