[QPID-7243] Make legacy JMS client publish messages with domain qualified userid

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 02/May/16 12:16
• Updated: 10/Dec/18 10:48
• Resolved: 30/Jan/18 17:22

Description

The Java Client currently populates JMSXUserId of published messages with the userid that the client used to authenticate to the Broker. When the client is in use with the Java Broker which supports the feature, it should pass the domain qualified name, supplied by the Broker instead.

To do this, message source $virtualhostproperties will have an extra header authenticatedUser which will contain the serialised form of the principal. If this is populated, the client MUST use this value in preference to the value it used when it authenticated.

Issue Links

• is related to: QPID-7092 User identity must be unique