LDAP Error: Invalid credentials

Revision as of 16:54, 29 April 2015 by Jderrick (talk | contribs) (Initial Edit.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

What was the error?

Message Number: 384

Message Severity: Error (Corrective action required to proceed)

Message Name: ARS0384E

Message Text:

LDAP Error: Invalid Credentials -- ldap_rc=<RC> -- extended+rc=<RC>, Success -- ldap_errno=<RC>, extra_rc=<RC> File=arsldap.c, Line=<LineNo>

where <RC> is the return code, and <LineNo> is the line in the source code where the error was caught. See below for more information on common return codes and their meanings.

Related Errors

ARS0436E

What were you doing?

Probably attempting to configure LDAP on Content Manager OnDemand for the first time, or a user attempted to authenticate with a bad user id or password on an LDAP-enabled CMOD server.

What happened?

The LDAP server couldn't authorize the user to perform an action, because the User ID or password they provided was not correct. It may also indicate an error in your LDAP configuration.

Example

Troubleshooting

Ensure you are using the correct User ID or password.

Also, you may have incorrect configuration data in your stash file. See arsstash for an explanation of stash files, or LDAP and Content Manager OnDemand for a tutorial.

The return code 49 indicates that you likely have a configuration issue.


Common Active Directory return codes:
525 user not found
52e invalid credentials
530 not permitted to logon at this time
531 not permitted to logon at this workstation
532 password expired
533 account disabled
534 The user has not been granted the
requested logon type at this machine
701 account expired
773 user must reset password
775 user account locked