Re: [PATCH] Add an ldapoption to disable chasing LDAP referrals

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: James Sewell <james(dot)sewell(at)lisasoft(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add an ldapoption to disable chasing LDAP referrals
Date: 2013-10-19 02:00:05
Message-ID: 1382148005.21792.3.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2013-10-17 at 13:49 +1100, James Sewell wrote:

> The search+bind mode issue is one of documentation location, I have
> fixed it by moving the section to the applied to both list. As the
> patch is to do with post-auth response this is correct.
>
Makes sense.

> As far as the issue when something other than 0 or 1 is set I am happy
> throw an error (although this doesn't seem to be how option such as
> LDAPTLS work: 1 if 1 else 0).

Right, that's how ldapreferrals ought to work as well.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2013-10-19 03:21:17 Re: ERROR : 'tuple concurrently updated'
Previous Message Peter Eisentraut 2013-10-19 01:42:45 Re: libpgport vs libpgcommon