Red Hat Bugzilla – Bug 779580
Modify JMS Gateway for standard populatation of AuthenticationRequest for service authentication
Last modified: 2012-08-02 09:03:26 EDT
++ This bug is a clone of bug 779579 ++
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
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  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
This was triaged for SOA 5.1.0. Not in SOA 5.1.0
This will not be considered for SOA 4.3. Keeping 5.x only. Decision by SOA PM team triage meeting.