[
https://issues.apache.org/jira/browse/ARTEMIS-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771915#comment-17771915
]
ASF subversion and git services commented on ARTEMIS-4451:
----------------------------------------------------------
Commit ef5fb0b1f19fe6b0ba2a9dfb93dd2138433ed03f in activemq-artemis's branch
refs/heads/main from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ef5fb0b1f1 ]
ARTEMIS-4451: fix non-SASL AMQP connections when resource audit logging enabled
> non-SASL AMQP connection fails if resource audit logging enabled
> ----------------------------------------------------------------
>
> Key: ARTEMIS-4451
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4451
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.31.0
> Reporter: Robbie Gemmell
> Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If the resource audit logging is enabled, then previous connection related
> audit log changes cause non-SASL AMQP connections to always fail, with the
> broker indicating to the client that a SASL connection is required, even if
> the broker config is actually such that it should not be. Simply disabling
> the resource audit log in the logging config then allows the non-SASL
> connection to succeed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
