You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/06/04 16:04:00 UTC
[jira] [Commented] (ARTEMIS-1896) Centralize logging of
authentication failures
[ https://issues.apache.org/jira/browse/ARTEMIS-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500421#comment-16500421 ]
ASF subversion and git services commented on ARTEMIS-1896:
----------------------------------------------------------
Commit ef6e3948fd416996059fdd83568388c2eb44ab53 in activemq-artemis's branch refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=ef6e394 ]
ARTEMIS-1896 centralize authn failure logging
Authentication failures are currently only logged for CORE clients.
This change puts the logging in a central location which all protocols
use for authentication so that authentication failures are logged for
all protocols.
> Centralize logging of authentication failures
> ---------------------------------------------
>
> Key: ARTEMIS-1896
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1896
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
> Reporter: Lionel Cons
> Priority: Major
>
> In case of authentication failure with any protocol Artemis should log a warning with the faulty user name. This logging currently happens for core clients, but not for STOMP clients (and likely others as well).
> In my tests, the client does get a {{User name [foo] or password is invalid}} {{ERROR}} frame but the broker does not log anything.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)