[jira] [Closed] (ARTEMIS-4451) non-SASL AMQP connection fails if resource audit logging enabled

2023-10-25 Thread Clebert Suconic (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Clebert Suconic closed ARTEMIS-4451.


> 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
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 2.32.0
>
>  Time Spent: 40m
>  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)


[jira] [Closed] (ARTEMIS-4451) non-SASL AMQP connection fails if resource audit logging enabled

2023-10-25 Thread Clebert Suconic (Jira)


 [ 
https://issues.apache.org/jira/browse/ARTEMIS-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Clebert Suconic closed ARTEMIS-4451.

Resolution: Fixed

> 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
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: 2.32.0
>
>  Time Spent: 40m
>  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)