Bridging from HTTP+WS-Security to JMS with the WSO2 ESB
Submitted on March 10, 2008 - 00:08. Story : Level : Project :
In this introductory screen cast, Asankha Perera the Product Manager and the Architect of the WSO2 ESB, shows how easy it is to create a proxy service for an existing JMS service, and then introduce WS-Security at the proxy using a WS-Policy attachment.
Sorry, flash is not available.
(1 vote)
»
- Login or register to post comments
- Printer friendly version
- 1422 reads
Tag Cloud
Apache Rampart
Apache Synapse
Axis2
Axis2
Axis2/C
WSF/C
Axis2/C
Rampart/C
Data Services
data services
ESB
ESB
Synapse/Java
Rampart/Java
ESB/Java
AXIOM/Java
WSAS/Java
Sandesha2/Java
Axis2/Java
Mashup Server
Mule
OpenID
open source
PHP
WSF/PHP
Proxy Services
Rampart
rampart
Registry
REST
Sandesha2
security
SOA
soap
Spring
Synapse
Synapse
Training
webinar
Web Services
WS-Security
WSAS
WSAS
wsdl
wsf
WSF/C
WSF/PHP
WSO2
WSO2 Registry
WSO2 WSF/PHP











Quick question
Thanks for the excellent tutorial Asankha!
I did have one quick question -- If I were instead using PasswordDigest and wanted to validate the provided password, how would you suggest going about that?
For example, I'd like to validate the provided password, then strip off the WS-Security headers, such as in your example, and forward to a JMS queue.
Thanks,
jeff