[JBoss ESB Development] - Re: SAML Token Support
by beve
Adding a SAML Assertion to outgoing SOAP Messages
=================================================
In what situations should the Assertion be added to the outbound SOAP Security Header:
1. SOAP Processor
SOAPProcessor expects the Body of the ESB Message to be a SOAPMessage. We could use an action that updates/adds a Security Header to the SOAP Message.
This can be done by adding the following action:
<action name="addSamlSecurityHeader" class="org.jboss.soa.esb.smooks.SmooksAction">
| <property name="smooksConfig" value="/smooks/smooks-saml-injector.xml" />
| </action>
2. SOAPClient (soapUI)
This action uses soapui for its processing. SOAPUI creates the actual SOAP Message and returns it as a String. But this action also supports
a smooks tranformation. We can use the same Smooks confuration as shown above. So this could be used for the configuration of SOAPClient like this:
<property name="smooksTransform" value="/smooks/smooks-saml-injector.xml" />
3. SOAPClient (WISE)
Since WISE uses JAXWS then we should be able to use a protocol handler for SOAP to add the header.
WISE supports both specifying a 'smooksTransform', like the SOAPUI SOAPClient, and also custom handlers. One such handler can be found in
org.jboss.soa.esb.actions.soap.SOAPSamlHandler.
4. SOAPProxy
HTTPProxy also expects the Body of the ESB Message to be a SOAPMessage. Here too the same Smooks configuration can be used.
Anything you can think of that I've missed?
Thanks,
/Daniel
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256787#4256787
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256787
17 years, 1 month
[JBoss ESB Development] - Re: XPath Routing
by ammppp
Looking good guys! Only two other things I'd like to see here.
One is something similar to what someone else mentioned - basically allow the service name and category to optionally be xpath as well (basically destinations can be dynamic rather than picked from a static list). For example:
<destination target-category="/order/header/@category" target-service="/order/header/@service" expression="/order/header[@cat='red']/>
In this case, a previous action would have been responsible to set these attributes in the message or the other ESB service developers would be responsible to name the ESB services based on values already passed in the ESB message.
Second thing is that I'd like the xpath to not be restricted to the default message body. Would be nice to be able to pull this data (decision expression or service name or service category ) from some place other than just the default message body.
These same requests would apply to the regex router.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256763#4256763
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256763
17 years, 1 month