Home/ Questions/Q 427123
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T19:32:54+00:00

There is a password policy in place on OpenDS preventing i.e. multiple login failures.

  • 0

There is a password policy in place on OpenDS preventing i.e. multiple login failures. If user manages to pass the limit, the logs of LDAP server will show, i.e.:

[17/Oct/2009:17:51:11 +0200] BIND RES conn=91 op=0 msgID=1 result=49 authFailureID=197126 authFailureReason=”Rejecting a bind request for user uid=XXXXXXXX,ou=users,dc=XXXXXXX,dc=hr because the account has been locked due to too many failed authentication attempts” etime=1

How to receive the LDAP response code in ANY Java client API (on bind()) other than the “49”, which is a generic “Invalid Credentials” response for all kinds of errors that can happen. LDAPException in JLDAP, and Exception in JNDI don’t seem to contain any more useful information (to show to the user on the presentation layer) besides the “49” and the aforementioned “Invalid Credentials” message. Looking at the logs defeats the purpose of password policy entirely.

Any ideas?

Best regards,
Bozo

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Solved. It seems you can’t receive a numerical response, but you can turn on (in OpenDS config) error messages on bind, and then you have to parse response into your application codes for failed login. Ridiculous.

    • 0