[
https://issues.apache.org/jira/browse/DIRAPI-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705209#comment-17705209
]
Natan Abolafya commented on DIRAPI-387:
---------------------------------------
Hi! Thanks Emmanuel.
Yes, that's normally the case when we get an *LdapException* but not the case
in {*}PasswordException{*}. It has an *ldapException* field but it is null. At
least as far as I can see. Check the debug screenshot I have attached on the
issue.
> More info on PasswordException
> ------------------------------
>
> Key: DIRAPI-387
> URL: https://issues.apache.org/jira/browse/DIRAPI-387
> Project: Directory Client API
> Issue Type: Improvement
> Reporter: Natan Abolafya
> Priority: Minor
> Attachments: debug.png
>
>
> It would be nice to get more info on PasswordException.
> Here is a response coming from Active Directory.
>
> {code:java}
> Message ID : 7
> BindResponse
> Ldap Result
> Result code : (INVALID_CREDENTIALS) invalidCredentials
> Matched Dn : ''
> Diagnostic message : '80090308: LdapErr: DSID-0C090446, comment:
> AcceptSecurityContext error, data 533, v4563 '
> ){code}
>
>
> The information in Diagnostic message can be quite useful sometimes. In this
> case, the "data 533" means the account is disabled which would be quite
> useful information for diagnostics. I am attaching how the exception looks
> like on debugger also.
>
> Normal LdapExceptions have this information but not the PasswordException. It
> would be really nice to add it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
