You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/06/08 10:40:21 UTC
[jira] [Updated] (QPID-7243) Make legacy JMS client publish
messages with domain qualified userid
[ https://issues.apache.org/jira/browse/QPID-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7243:
-----------------------------
Fix Version/s: (was: qpid-java-6.1)
qpid-java-6.2
> Make legacy JMS client publish messages with domain qualified userid
> --------------------------------------------------------------------
>
> Key: QPID-7243
> URL: https://issues.apache.org/jira/browse/QPID-7243
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Keith Wall
> Fix For: qpid-java-6.2
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org