Hi all! I have this problem, can't find solution for few days and that makes me crazy. I have configured jaxws client and STSClient as described http://cxf.apache.org/docs/ws-trust.html. When I run client program, I get this exception: org.apache.cxf.binding.soap.SoapFault: The message with Action 'http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
That's because STSCLient is generating http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue for Action header value. However STS client is expecting http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue and request fails. However, if I create STS client programmaticaly, header contains correct Action. what could be wrong? This is piece of sts issuer wsdl: <wsdl:portType name="IWSTrust13Sync"> <wsdl:operation name="Trust13Issue"> <wsdl:input wsaw:Action="http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue"; message="tns:IWSTrust13Sync_Trust13Issue_InputMessage"/> <wsdl:output wsaw:Action="http://docs.oasis-open.org/ws-sx/ws-trust/200512/RSTRC/IssueFinal"; message="tns:IWSTrust13Sync_Trust13Issue_OutputMessage"/> </wsdl:operation> </wsdl:portType> p.s. I tried with cxf 2.6.0 and laters. -- View this message in context: http://cxf.547215.n5.nabble.com/STSClient-SOAP-Action-tp5713451.html Sent from the cxf-user mailing list archive at Nabble.com.
