[
https://issues.apache.org/jira/browse/ARTEMIS-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4767.
-------------------------------------
Assignee: Justin Bertram
Resolution: Won't Fix
I don't believe there's a reliable, tamper-proof way to detect that the message
was sent via a cluster-connection in order to avoid setting the validated user
to the cluster user. Therefore, I'm closing this.
> Original JMSXUserID is lost on message redistribution
> -----------------------------------------------------
>
> Key: ARTEMIS-4767
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4767
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 2.33.0
> Reporter: Michael Desmedt
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> when {{populate-validated-user}} is set to true, in a clustered configuration:
> if both the producer and the consumer are on the same broker, when a message
> is sent with user1, consumed message contains property {{JMSXUserID:user1}}
> if the producer and the consumer are on different brokers in the same
> cluster, when a message is sent with user1, the consumed message contains
> property {{JMSXUserID:<value of <cluster-user>>}}
>
> initial validated-user value is lost.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
