[QPID-7244] Expose realm qualified authenticate name to messaging clients

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Future
• Component/s: Broker-J
• Labels: Broker-J-Identity
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 02/May/16 12:19
• Updated: 04/Jun/18 10:51

Description

We want messaging clients to be capable of publishing messages with the JMSXUserId populated with a realm qualified authenticated name.

To enable this for 0-8..0-10 change message source $virtualhostproperties to have an extra header authenticatedUser which will contain the serialised form of the principal. For 1.0, a non-normative (probably qpid specific) connection property could be used by the open performative (discussion required).

The Java Broker messageAuthorizationRequired feature must be relaxed to allow either the the realm qualified form, or bare form. The latter is required for compatibility with clients which don't support the feature.

Issue Links

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