>> Default port for LDAPS:// is 636. I verified with "ldapsearch" tool that it works with that port.
Odd, in my integration work b/w Apache on Linux and Windows AD, it didn't work well with port 636. Yet, it did work well with port 3269.
Cheers,
-ar
On Fri, Aug 11, 2017 at 12:00 PM, Tang, Ronald K CIV FNMOC, N6 <ronald.k.tang@navy.mil> wrote:
I am responding to all replies in this single email. Thanks for all your response.
>> The ldapserver= attribute takes a host name, not a URL. Thanks. I tried that too. If I omit the ldaps:// the response is server not found.
>> What OS is your server running, and what OS is your client running? RedHat Linux (RHEL 6), both client and server. Postgres 9.5.6
>> Well, first off, you're on the wrong port for LDAPS:// Default port for LDAPS:// is 636. I verified with "ldapsearch" tool that it works with that port.
Thanks, Ron
-----Original Message----- From: Peter Eisentraut [mailto:peter.eisentraut@2ndquadrant.com] Sent: Thursday, August 10, 2017 8:05 PM To: Tang, Ronald K CIV FNMOC, N6; pgsql-admin@postgresql.org Subject: [Non-DoD Source] Re: [ADMIN] Postgres user authentication with secure LDAP
On 8/10/17 17:02, Tang, Ronald K CIV FNMOC, N6 wrote: > I am trying to configure my Postgres server to use LDAP for authentication. My pg_hba.conf config line is: > > ldap ldapserver=ldaps://myldaps.company.com ldapport=636 ldaptls=1 ldapprefix="uid=" ldapsuffix=",ou=People,o=my.company.com"
The ldapserver= attribute takes a host name, not a URL. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services