|
| It seems I always get stuck on the basics. :-)
WebSphere 6.1, AST
I've developed a EJB web service and a webapp (servlet/jsf) web service client. They're now working together fine.
However, when I went to add an XML Signature to the web service request, I ran into a problem. I've tried both using the AST wizards and manually updating the client and service deployment descriptors as described in the WebSphere 6.1 Web Services handboo
k. Whichever way I try, my service seems to be now expecting the signature but my client never adds anything to the request (confirmed by TCPMonitor).
I've gone over my webapp client deployment descriptors a number of times and they seem to match what is described in the handbook. Of course, the client behaves the same even if I use the AST wizard..
No error messages in the WebSphere logs other than the service complaining it can't find the security header. (I'm not surprised, it's not being sent.) I even activated tracing but I couldn't find any clue there either.
Anyone have any idea what I might be missing? I could see if my client generated some security output that was inconsistent with what the service expected, or missing keys, certificates, etc... but I'm not even getting started!
Thanks in advance,
Mike.
|
|