[ http://issues.apache.org/jira/browse/SYNAPSE-41?page=all ]
Asankha C. Perera resolved SYNAPSE-41.
--------------------------------------
Fix Version/s: Incubating-0.90
Resolution: Fixed
Fixed with a sample to demonstrate the correct behaviour and related
documentation
> When Synapse is used to talk to a WS-Sec endpoint, the response back to the
> [non WS-Sec] client is encrypted
> ------------------------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-41
> URL: http://issues.apache.org/jira/browse/SYNAPSE-41
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Fix For: Incubating-0.90
>
>
> This is because the same Axis2 message context for the incoming message was
> used to send out the request to the endpoint. During this process the message
> context is altered to use WS-Security, and the response received has WS-Sec
> as well. The response is now received to Synapse decrypted, but when its sent
> out again, Rampart gets engaged to re-encrypt is before sending back to the
> client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
