I've been a little quiet on the blogging front recently while working on a number of JAX-WS WS-Security solutions via JDeveloper 11g and WebLogic Server 10.3, an area I'm no expert, but rapidly gaining an appreciation of the complexities. Gerard Davison from Oracle UK has been incredibly helpful in finding solutions to my numerous questions about how to get all this working, his blog is well worth checking out if you're interested in JEE web services.
As I've received a number of emails from others on how to get WS-Security working with the new JAX-WS offerings in JDeveloper 11g and WLS 10.3, can I recommend readers check out this post from Gerard that shows the essential steps in configuring both the server and client side working with the numerous required digital certificates. Once you have that up an running it's fairly easy to extend Gerard's example to include the SOAP body WLS encryption policy (Wssp1.2-2007-EncryptBody.xml) - though make sure you read Gerard's Feb 11th update in the same post as it has an essential fix.
Happy web servicering.
As I've received a number of emails from others on how to get WS-Security working with the new JAX-WS offerings in JDeveloper 11g and WLS 10.3, can I recommend readers check out this post from Gerard that shows the essential steps in configuring both the server and client side working with the numerous required digital certificates. Once you have that up an running it's fairly easy to extend Gerard's example to include the SOAP body WLS encryption policy (Wssp1.2-2007-EncryptBody.xml) - though make sure you read Gerard's Feb 11th update in the same post as it has an essential fix.
Happy web servicering.
2 comments:
Chris Muir,
I can't find the Gerard's Feb 11th update. What is that essential fix there?
What, not even a pretty please?
It's at the end
of this post as an addendum: http://kingsfleet.blogspot.com/2009/01/security-policy-worked-example.html
CM.
Post a Comment