You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Shripad Gokhale <sh...@amdocs.com> on 2008/08/04 14:27:53 UTC
WSDoAllReceiver: security processing failed (actions mismatch)
I am getting following error. What can be the reason for this?
<faultstring>WSDoAllReceiver: security processing failed
(actions mismatch)</faultstring>
I am sending following header as part of request.
<soapenv:Header>
<wsse:Security soapenv:mustUnderstand="1">
<wsu:Timestamp
wsu:Id="Timestamp-3bcdc3b0-ada1-414a-bcc3-2ba7c805fdba">
<wsu:Created>2008-07-10T17:42:24Z</wsu:Created>
<wsu:Expires>2008-07-10T17:47:24Z</wsu:Expires>
</wsu:Timestamp>
<wsse:UsernameToken
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd"
wsu:Id="SecurityToken-bf8a70e3-3936-4b50-8c9e-213b08fd5a1f">
<wsse:Username>IDMTEST</wsse:Username>
<wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t
oken-profile-1.0#PasswordText">iptv4all</wsse:Password>
<wsse:Nonce>YpoCIr2Dde9LddBMU5k7wg==</wsse:Nonce>
<wsu:Created>2008-07-10T17:42:24Z</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
My server-config.wsdd looks like following.
<service name="SOAP_Server" provider="java:RPC">
<requestFlow>
<handler
type="java:org.apache.ws.axis.security.WSDoAllReceiver">
<parameter
name="passwordCallbackClass"
value="PWCallback"/>
<parameter name="action"
value="Timestamp UsernameToken"/>
</handler>
</requestFlow>
<parameter name="className" value="bl.SOAPServerSOAP_Server"/>
<parameter name="allowedMethods" value="*"/>
<beanMapping
languageSpecificType="java:bl.SOAPServerSOAP_Server$Record_2Parameter"
qname="myNS:Record_2" xmlns:myNS="urn:SOAP_Server"/>
<beanMapping
languageSpecificType="java:bl.SOAPServerSOAP_Server$Record_1Parameter"
qname="myNS:Record_1" xmlns:myNS="urn:SOAP_Server"/>
</service>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp