[
https://issues.apache.org/jira/browse/ARTEMIS-4451?focusedWorklogId=883379&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-883379
]
ASF GitHub Bot logged work on ARTEMIS-4451:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Oct/23 16:10
Start Date: 04/Oct/23 16:10
Worklog Time Spent: 10m
Work Description: gemmellr opened a new pull request, #4642:
URL: https://github.com/apache/activemq-artemis/pull/4642
Ensure the eligibility check done can succeed with the audit logging
enabled, allowing non-SASL connections if broker config allows (rather than
erroneously failing and indicating SASL is required when it shouldnt be).
Issue Time Tracking
-------------------
Worklog Id: (was: 883379)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
