Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
closing this in liue of solution #2423
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
alternative option 1 - https://github.com/apache/activemq-artemis/pull/2423
---
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
@tabish121 im open to suggestion on how to implement this in a way thats
more amenable to yourself.
Other ideas i have:
1) Introduce a broker flag that
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
@tabish121 ok, so the use case here, is per
https://issues.apache.org/jira/browse/ARTEMIS-584 essentially you cannot/do not
trust the user sent on the message, you only trust
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
@michaelandrepearce I may have worked due to a bug that allowed the broker
to violate the AMQP specification but was fixed later
(https://issues.apache.org/jira/browse/ARTEMIS-1092) and
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
@tabish121 this used to work. Also note this is only when the toggle
populate-validated-user is enabled, which is off by default.
---
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2422
-1
The properties section of an AMQP message is immutable and cannot be
changed by the broker as per the AMQP 1.0 specification (Section 3.2)
