[ 
https://issues.apache.org/jira/browse/WSS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Naresh Kumar Sampath updated WSS-207:
-------------------------------------


Hi all,

I have figured out where I am wrong.

I was using SOAPMonitor of AXIS to view the soap message. In the Web service 
deployment descriper , I have included the WSDoAllReceiver handler and then 
followed by the SOAPMonitor handler. By the time the control reaches the 
soapmonitor handler, the soap message is decrypted. So in the SOAPMonitor the 
decrypted message is being displayed.

Regret for the inconvenience. I appreciate the effort of colm and R1ch. Thanks 
a lot.

Regards,
Naresh

> The Soap Message is not getting encrypted.
> ------------------------------------------
>
>                 Key: WSS-207
>                 URL: https://issues.apache.org/jira/browse/WSS-207
>             Project: WSS4J
>          Issue Type: Test
>          Components: WSS4J Handlers
>         Environment: Windows Machine
>            Reporter: Naresh Kumar Sampath
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>         Attachments: Steps followed for wss4j.zip
>
>
> Hi,
> I am using  WSS4j - 1.5.8 and XML sec - 1.3.0 .
> I have added the WSDoAllSender handler in the Requestflow. The soap message 
> is being created and transfered to the server and I am gettign the response 
> from the server with out any exception.
> But when i look in to the soap message the message is being transfered as 
> plain text. In the header part the symmetric key is encrypted where as the 
> soap body is not getting encrypted.
> I assume that i am missing out a configuration. Please help me to resolve 
> this issue.
> Thanks
> Naresh

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to