[
https://issues.apache.org/jira/browse/DIRAPI-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059109#comment-17059109
]
Emmanuel Lécharny commented on DIRAPI-355:
------------------------------------------
Actually, this message is set when the Ldap result code is not one of
NO_SUCH_OBJECT, ALIAS_PROBLEM, INVALID_DN_SYNTAX or
ALIAS_DEREFERENCING_PROBLEM. It's a catch all message. It does not necessarily
means your credentials is not correct, it might also been that the user's DN is
not correct. Actually, there is no way to know which one of the two is failing.
Now, if you don't want this message to be logged at all, you can modify the
log4j.property file to disable the
{{org.apache.directory.api.ldap.codec.actions.ldapResult.StoreMatchedDN}}
logger.
> Binding with wrong credentials is logged in StoreMatchedDN at WARN level
> ------------------------------------------------------------------------
>
> Key: DIRAPI-355
> URL: https://issues.apache.org/jira/browse/DIRAPI-355
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Boris Petrov
> Priority: Minor
>
> Calling `connection.bind(user, pass)` when the credentials are wrong causes:
> {noformat}
> 16:00:44.094 [NioProcessor-6] WARN o.a.d.a.l.c.a.l.StoreMatchedDN -
> MSG_05107_NO_SUCH_OBJECT_MATCHED_DN_NOT_SET ()
> {noformat}
> Which is not very nice. Entering wrong credentials is a perfectly normal
> operation and I don't see why a warning would be issued. It is annoying
> because we have to suppress these.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
