You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2010/01/11 18:18:54 UTC

[jira] Updated: (CXF-2459) Allow setting SecurityContext from JMS Message for Tibco JMS

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

Daniel Kulp updated CXF-2459:
-----------------------------

    Fix Version/s:     (was: 2.3)
                   2.2.6

> Allow setting SecurityContext from JMS Message for Tibco JMS
> ------------------------------------------------------------
>
>                 Key: CXF-2459
>                 URL: https://issues.apache.org/jira/browse/CXF-2459
>             Project: CXF
>          Issue Type: New Feature
>          Components: Transports
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>            Priority: Minor
>             Fix For: 2.2.6
>
>
> 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.
> As the property can be set by users for jms providers other than Tibco we can not simply always take it. I think we need a configuration option that tells CXf if it should honor the above property.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.