. Advertisement .
..3..
. Advertisement .
..4..
I encountered the following problem in completing my work:
ldap_bind: Invalid Credentials (49).Below is the code I ran:
$ ldapsearch -x -W -D 'cn=Manager,dc=example,dc=com' -b "" -s base# slapd.conf - Configuration file for LDAP SLAPD
##########
# Basics #
##########
include /etc/ldap/schema/core.schema
include /etc/ldap/schema/cosine.schema
include /etc/ldap/schema/inetorgperson.schema
pidfile /var/run/slapd/slapd.pid
argsfile /var/run/slapd/slapd.args
loglevel none
modulepath /usr/lib/ldap
# modulepath /usr/local/libexec/openldap
moduleload back_hdb
##########################
# Database Configuration #
##########################
database hdb
suffix "dc=example,dc=com"
rootdn "cn=Manager,dc=example,dc=com"
rootpw secret
directory /var/lib/ldap
# directory /usr/local/var/openldap-data
index objectClass,cn eq
########
# ACLs #
########
access to attrs=userPassword
by anonymous auth
by self write
by * none
access to *
by self write
by * none# LDAP Client Settings
URI ldap://localhost
BASE dc=example,dc=com
BINDDN cn=Manager,dc=example,dc=com
SIZELIMIT 0
TIMELIMIT 0What’s causing it, and how can it be resolved in the “ldap_bind: invalid credentials (49)“ in the programs?
The cause: The XMS cannot connect as the Bind User to perform a role or group lookup because the BIND credentials are invalid. Therefore, it leads to the ldap_bind: invalid credentials (49) error.
Solution:
BIND name and perhaps BIND password must be entered correctly.
When setting the bind password using the XMCLI, the same restriction on special characters is not present. However, if the password is changed using any of those special characters, XMS Recovery won’t function later if necessary, including when a new XMS is replacing an old XMS. When changing the BIND password, it is strongly advised that you utilize the WebUI. If possible, avoid using the characters listed in the KB article linked above when changing passwords using the XMCLI approach.