Bug 779579 (SOA-1954)

Summary: Modify JMS Gateway for standard populatation of AuthenticationRequest for service authentication
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Stelios Koussouris <skoussou>
Component: SwitchYardAssignee: Ken Johnson <kejohnso>
Status: NEW --- QA Contact: Matej Melko <mmelko>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: atangrin, ganandan, jackalista, jdbrown, ldimaggi, soa-p-jira, tasato
Target Milestone: ---   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1954
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 779580 (view as bug list) Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Stelios Koussouris 2010-02-17 15:06:06 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=461273&gid=6022
project_key: SOA

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
Comment 1 Anne-Louise Tangring 2010-09-21 20:18:43 UTC 
This was triaged for SOA 5.1.0. Not in SOA 5.1.0
Comment 2 Anne-Louise Tangring 2011-02-22 19:29:52 UTC 
This will not be considered for SOA 4.3. Keeping 5.x only. Decision by SOA PM team triage meeting.