Re: LDAP authentication fails with concurrent create extensions - Mailing list pgsql-bugs

From Greg k
Subject Re: LDAP authentication fails with concurrent create extensions
Date
Msg-id CAC5zpv3CY0y5okrgeBF=Sqxfi-yOO_LWiVr-rHPn6_4cGzb8Dw@mail.gmail.com
Whole thread Raw
In response to Re: LDAP authentication fails with concurrent create extensions  (Stephen Frost <sfrost@snowman.net>)
Responses Re: LDAP authentication fails with concurrent create extensions
List pgsql-bugs
Hi Stephen,

Do I need to raise this as an issue or bug?

Thanks,
Greg

On Tue, 10 Apr 2018 at 21:31 Stephen Frost <sfrost@snowman.net> wrote:
Greetings,

* Greg k (gregg.kay@gmail.com) wrote:
> We are using postgresql 10.3 on Centos 7.2 with LDAP authentication (samba4
> with AD domain controller). We've recently moved to LDAP authentication and
> are now encountering a problem where some concurrent connections that
> create extensions in different databases at the same time are failing with
> a "Can't contact LDAP server" error. The postgres error log contains:

You really shouldn't be using LDAP in an AD environment for
authentication- configure and use Kerberos instead, which is much more
secure than having cleartext passwords seen by the PG server and then
proxied to the LDAP server.

That said, there does appear to be an issue here, thanks for creating a
test case.

Stephen

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Ignored join clause
Next
From: Thomas Munro
Date:
Subject: Re: LDAP authentication fails with concurrent create extensions