From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | C GG <cgg0007(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: LDAP authentication slow |
Date: | 2018-05-30 21:43:15 |
Message-ID: | 6990674a-9be4-e185-3cad-3af5f76fc821@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/30/2018 01:41 PM, C GG wrote:
>
>
> Please let me be clear, this is not a question about whether or not to
> use passwords. This is a question of how to determine the cause of and
> remedy a slowdown retrieving data from PostgreSQL when using LDAP(S) to
> authenticate PostgreSQL users. One of the sideline questions would be
> how to achieve the same effect by using a different scheme. I should
> further clarify that a major requirement would be that the scheme would
> need to work in our current environment without having to re-engineer
> the client applications. That would entail the need to pass a username
> and password as we have traditionally done.
>
> Any friendly assistance with LDAP(S) to that end is welcome.
Have been following this thread and have not answered previously as
LDAP/AD is not something I really know about. Still strikes me as
similar to another LDAP thread:
In that post the OP found that supplying an IP address instead of a host
name sped up the process.
Have you tried that?
It may not be a permanent solution, but it might help identify where the
problem is.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | C GG | 2018-05-30 22:10:24 | Re: LDAP authentication slow |
Previous Message | C GG | 2018-05-30 20:41:37 | Re: LDAP authentication slow |