[esb-issues] [JBoss JIRA] (JBESB-3742) Modify JMS Gateway for standard populatation of AuthenticationRequest for service authentication

[RH Bugzilla Integration (JIRA)]

     [ https://issues.jboss.org/browse/JBESB-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated JBESB-3742:
-------------------------------------------

    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=779580  (was: https://bugzilla.redhat.com/show_bug.cgi?id=779580)

    
> Modify JMS Gateway for standard populatation of AuthenticationRequest for service authentication
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBESB-3742
>                 URL: https://issues.jboss.org/browse/JBESB-3742
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Message Store
>    Affects Versions: 4.11
>            Reporter: Tom Cunningham
>
> The customer is looking to pass credentials via a JMS client so that the JMS gateway can pull those credentials from the transport(message) and create an AuthenticationRequest object that is used to authenticate against a "secured" service. What he is looking for is standard functionality similar of that of the JBR Gateway [1] rather than having to enhance the Gateway with a custom composer class.
> In addition, clarification on which Gateways actually currently offer this functionality and "how" the client can provide the credentials would be useful
> [1] http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/rosetta/src/org/jboss/soa/esb/listeners/gateway/JBossRemotingGatewayListener.java

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