cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Rhenius (JIRA)" <>
Subject [jira] Created: (CXF-3365) CXF uses wrong policy alternative on response message
Date Fri, 25 Feb 2011 10:49:39 GMT
CXF uses wrong policy alternative on response message

                 Key: CXF-3365
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 2.3.2
            Reporter: Karl Rhenius

CXF uses a wrong policy on outgoing messages, if the wsdl has alternative policies.

Here is my setup:
	#1 SecureConversation policy
	#2 nothing special, clients just send an UsernameToken

	#1 SecureConversation policy

The client defines only the SecureConversation policy in it's wsdl.

If I test my service, they communicate like this:
Client > Server: RST/SCT message
Server > Client: answers with a token
Client > Server: calls the webservice with an encrypted soap message
Server > Client: answers the service call with an unencrypted message
(the server took policy #2 for the answer) -> client throws an exception
"These policy alternatives can not be satisfied"

I attached a test project, based on the AC_IPingService from the interop samples.
You can change the wsdl, which will be used by the server, in WSSCTest.startServers().

Related to this issue is the following bug:

If the UsernameToken policy is defined before the SecureConversation policy, the webservice
fails on the RST/SCT message. Start the server with UtSecConvIPingService() to test this.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message