LOG","00000","could not initialize LDAP: Bad parameter to an ldap routine

Products

• VMware Tanzu Greenplum

Issue/Introduction

Unable to set up LDAP, ldap fails to start when an LDAP user tries to connect with the following message in the master logs. 

 

"LOG","00000","could not initialize LDAP: Bad parameter to an ldap routine"

Cause

A wrong ldap option was used when populating the pg_hba.conf. This is an example of an incorrect pg_hba.conf entry

host all johnd 0.0.0.0/0 ldap ldapserver="ldap://bc.net" ldappport=389 ldapsearchattribute=sAMAccountName ldapbasedn="DC=bc,DC=net" ldapbinddn="CN=GreenPlum bind,OU=Service Account,DC=bcb,DC=net" ldapbindpasswd="xxxxxxx

The ldapserver entry is using ldap:// which is not allowed

Resolution

ldapserver should not use "ldap://.."; ldap:// is is for ldapurl.
ldapserver should use the hostname or an ip address

 

Example

host all johnd 0.0.0.0/0 ldap ldapserver="ldap.bc.net" ldapport=389 ldapsearchattribute=sAMAccountName ldapbasedn="DC=bc,DC=net" ldapbinddn="CN=GreenPlum bind,OU=Service Account,DC=bc,DC=net" ldapbindpasswd="xxxxxx" 

or

host all johnd 0.0.0.0/0 ldapldapurl="ldap://10.0.0.134" ldapport=389 ldapsearchattribute=sAMAccountName ldapbasedn="DC=bc,DC=net" ldapbinddn="CN=GreenPlum bind,OU=Service Account,DC=bc,DC=net" ldapbindpasswd="xxxxxx"