You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2012/08/07 14:51:09 UTC

[jira] [Closed] (SMXCOMP-88) Forward authenticated jms user to service

     [ https://issues.apache.org/jira/browse/SMXCOMP-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider closed SMXCOMP-88.
--------------------------------------

    Resolution: Won't Fix

Closing my issue as I do not use servicemix since some time
                
> Forward authenticated jms user to service
> -----------------------------------------
>
>                 Key: SMXCOMP-88
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-88
>             Project: ServiceMix Components
>          Issue Type: New Feature
>          Components: servicemix-jms
>            Reporter: Christian Schneider
>
> A jms endpoint that offers a soap/jms service should read the authenticated username from the jms message and forward it through the 
> message exchange to the called service. So this service can do further authorisation.
> To send the username the jms provider has to be configured with a special option.
> In Tibco you have to add the following line to queues.conf: > sender_name_enforced. This means that tibco should add the authenticated user name in the jms property JMS_TIBCO_SENDER to every message in every queue.
> In ActiveMq I have found from the documentation that you can use the option populateJMSXUserID. Then ActiveMQ sets the property JMSXUserID.
> From these configuations we see that the username can be in different properties depending on the jms server. So we have to add a configuation option to tell servicemix how to retrieve the username from the message. 
> The documentation should help with configuring the jms server. Perhaps we can find the necessary settings for other jms servers too like IBM MQ.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira