PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID16066
PG Version10.10
OSUbuntu 18.04
Opened2019-10-18 19:47:56+00
Reported byYudhveer Kandukuri
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      16066
Logged by:          Yudhveer Kandukuri
Email address:      (redacted)
PostgreSQL version: 10.10
Operating system:   Ubuntu 18.04
Description:        

Here are the pg_hba.conf entry for ldap.....

host      Tom           Tom           10.10.117.43/32         ldap 
ldapserver=10.10.117.43 ldapbasedn="ou=People,dc=internal,dc=g2llc"
ldapbinddn="cn=svc_ldap,ou=People,dc=internal,dc=g2llc"
ldapbindpasswd="Test123#" ldapport=389 ldapsearchattribute="uid"

When I am trying to connect to postgresql on remote server, I am getting the
message as no entry for "Tom" in pg_hba.conf file where the postgresql is
running on the remote server.

Already created the user "Tom" in postgresql and also created the user "Tom"
in ldap and also created one more ldap user account "i.e., svc_ldap" in
ldap.

Not Sure..what else I need to configure to make the Postgresql user to
authenticate with ldap

Thanks and regards
Yudhveer Kandukuri

Messages

DateAuthorSubject
2019-10-18 19:47:56+00PG Bug reporting formBUG #16066: Ldap Authentication failure on PostgreSQL 10.10
2019-10-18 23:12:23+00Stephen FrostRe: BUG #16066: Ldap Authentication failure on PostgreSQL 10.10