You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2018/06/04 10:05:00 UTC
[jira] [Updated] (QPID-7244) Expose realm qualified authenticate
name to messaging clients
[ https://issues.apache.org/jira/browse/QPID-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-7244:
-----------------------------
Fix Version/s: (was: qpid-java-broker-7.1.0)
Future
> Expose realm qualified authenticate name to messaging clients
> -------------------------------------------------------------
>
> Key: QPID-7244
> URL: https://issues.apache.org/jira/browse/QPID-7244
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Keith Wall
> Priority: Major
> Fix For: Future
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org