Ruwan Linton wrote:
stlecho wrote:
Ruwan,
Not sure I've understood your explanation. Anyway, the referenced
Jira issue
(SYNAPSE-355) exactly describes my problem. I thought that the
earlier in
this post mentioned SYNAPSE-127 issue solved my issue, but apparantly
it is
not :o(.
Any idea when this fix will be made available ?
We are planing on a quick point release of ESB/Synapse and it will be
available within next 3 weeks, but I will be fixing this by the end of
this week or early next week.
Hi Stefan,
I tried to fix this issue and found there is an issue in Rampart which
permits the behavior being implemented on Synapse, and filed an issue
for that. Once it has been fixed there, we can fix the issue and you can
use this as follows;
If you want to apply service level policies, (that is the same policy
for both in and out messages) you can use the existing behavior;
<enableSec policy="key"/>
If you need message level policies after the Rampart fix you should be
able to specify different policies for messages as follows;
<enableSec inboundPolicy="key" outboundPolicy="key"/>
In effect if you need only messages going to the service to be signed
and expect unsigned messages from the actual service, then you can drop
the inboundPolicy attribute and provide the policy key for signing to
the outboundPolicy attribute.
Thanks,
Ruwan
Thanks,
Ruwan
Regards, Stefan.
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
