[
https://issues.apache.org/jira/browse/AMQ-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3183.
-----------------------------
Resolution: Fixed
useAuthenticatedPrincipalForJMXUserID can be used in conjunction with
populateJMSXUserID to effect the userName based on the first authenticated user
principal.
http://svn.apache.org/viewvc?rev=1071301&view=rev
> Set JMSXUserID value based on authenticated principal
> -----------------------------------------------------
>
> Key: AMQ-3183
> URL: https://issues.apache.org/jira/browse/AMQ-3183
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: Authentication, JAAS,, JMSXUserID
> Fix For: 5.5.0
>
>
> When using the JaasDualAuthenticationPlugin, a user with id 'system' can gain
> the guest credentials but still remain with the 'system' username which gets
> into a produced message via the JMSXUserID property.
> It would be nice if the userName reflected the first authenticated
> UserPrincipal, such that a user 'system' authenticated to default role
> 'guest' after a failed login, proceeds to use the 'guest' userName.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
