[
https://issues.apache.org/jira/browse/DIRSERVER-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Ayyagari resolved DIRSERVER-1676.
---------------------------------------
Resolution: Fixed
Assignee: Kiran Ayyagari
Thanks for confirming, and I totally forgot about the ppolicy enum, that is the
way to compare.
> Provide a set of error codes along with an AuthenticationException to
> indicate its root cause.
> ----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1676
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1676
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 2.0.0-M4
> Environment: 64bit Windows, using 32 bit jvm to support wrapper.dll
> Reporter: Carlo Accorsi
> Assignee: Kiran Ayyagari
> Priority: Minor
> Labels: apacheds
> Fix For: 2.0.0-M16
>
>
> There may be more cases to consider but when a user supplies an incorrect
> password or the account is locked,
> a javax.naming.AuthenticationException is thrown. Currently comparing the
> strings returned by ex.getMessage() is
> the only way to determine which event occurred.
> [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot
> authenticate user uid=xyz,o=corp]
> [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: account was
> permanently locked]
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
