Highlighted
Trusted Contributor.
Trusted Contributor.

Re: ldap_start_tls: Connect error (-11)

Hi John,

 

Thanks for the suggestion. Here's the output :

which ldapsearch
/opt/iam/eDirectory/opt/novell/eDirectory/bin/ldapsearch

It looks like it's returning the Novell directory.

 

Can you please suggest on the same.

0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

Re: ldap_start_tls: Connect error (-11)

Hi mudit_gupta,

I am on RHEL 7.6 here, IDM 4.7.3/eDir 9.1.4 installed. The following statement works fine to query the directory (for a quick try):

LDAPTLS_REQCERT=never ldapsearch -H ldap://[server-FQDN]:389 -ZZ -x -D "[user LDAP DN]" -w [pwd] -b "cn=Status,cn=Agent,cn=Monitor" -s sub -a always -z 100000

 

Maybe important to mention: When going via TLS on 389 should not define ldaps as connection protocol.

Hope this helps...

Best regards,

Philipp

Highlighted
Respected Contributor.
Respected Contributor.

Re: ldap_start_tls: Connect error (-11)

Perfect, pborenich. Thanks. I was looking for this also now that eDirectory's ldapsearch has gone openldap.

Have generalized as:

LDAPTLS_REQCERT=never ldapsearch -h localhost:389 -ZZ -x -D "cn=admin,o=mytree" -W -b "o=mytree" -s sub -a always -z none "({some-ldap-query})" {some-attributes}

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.