Pavel
Sorry I missed the policy file.. this seems like an enhancement like
SYNAPSE-127 for the endpoint side.. currently only proxy policies
supports different in/out policies and not endpoints.. can you raise a
JIRA for this?
asankha
Asankha C. Perera wrote:
Nandana / Pavel
I think Pavel is using a modified sample, so Nandana may not be able
to reproduce this..
Pavel, can you share this policy file too?.. I think this is now fixed
(https://issues.apache.org/jira/browse/SYNAPSE-127), but just needs to
be set at the policy correctly, and Nandana maybe able to point out
the mistake
asankha
Nandana Mihindukulasooriya wrote:
Hi Pavel,
Just went through the policy, it seems that the response needs
to have
a security header if it is applied at the service level. Will dig in
to the
sample and will try to see why this is not working correctly. Hope all I
need to do is to try the sample assuming you didn't do any other
configuration out of the ordinary.
thanks,
nandana
2008/6/6 Paul Fremantle <[EMAIL PROTECTED]>:
You might want to ask on Rampart dev list, but I think you need to use
message level policies.
Paul
On Fri, Jun 6, 2008 at 11:52 AM, Pavel Křehula <[EMAIL PROTECTED]>
wrote:
Hello,
please see attached. request is generated by synapse, response is
answer
from the service.
Pavel
Asankha C. Perera napsal(a):
Pavel
Can you share your configuration and any steps to reproduce this with
the
samples, and/or any TCPmon traces of the response message received
asankha
Pavel Křehula wrote:
Hello,
I'm going to use synapse for signing soap messages.
When I send signed message to server, I get error:
2008-06-06 09:54:39,596 [192.168.0.84-PAVEL3] [HttpClientWorker-1]
ERROR
ClientWorker Fault processing response message through Axis2
org.apache.axis2.AxisFault: SOAP header missing
at
org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invoke(Phase.java:317)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
at
org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:200)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.rampart.RampartException: SOAP header missing
at
org.apache.rampart.RampartEngine.process(RampartEngine.java:99)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
which in fack I'm able to understand because server response message
indeed is not signed and does not contain any header.
My question is how to configure rampart to accept such response.
I'm using same wss policy as client_policy_3.xml and Synapse 1.2
--
Best regards,
Pavel Krehula
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
