cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Kessler (JIRA)" <>
Subject [jira] [Updated] (CXF-5325) error when having alternative transport bindings in WSDL
Date Wed, 09 Oct 2013 14:12:42 GMT


Joerg Kessler updated CXF-5325:


> error when having alternative transport bindings in WSDL
> --------------------------------------------------------
>                 Key: CXF-5325
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Joerg Kessler
>             Fix For: 2.7.6
>         Attachments:
> Hi,
> we have received a WSDL from a WS provider that allows Basic Authentication or Client
Certificate Authentication. When I configure Client Certificate Authentication in the conduit
for my CXF WS consumer. I receive the following error
> WARNUNG: Interceptor for {}ZMTOM_CXF_IN#{}CXF_IN
has thrown exception, unwinding now
> Assertion of type {}HttpsToken
could not be asserted: HttpBasicAuthentication is set, but not being used
> 	at$HttpsTokenOutInterceptor.assertHttps(
> 	at$HttpsTokenOutInterceptor.handleMessage(
> 	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> 	at org.apache.cxf.endpoint.ClientImpl.doInvoke(
> 	at org.apache.cxf.endpoint.ClientImpl.invoke(
> If I just allow Client Certificarte it works. If in the WSDL Client Certificate is defined
first it works. If I use WSRM the Create Sequence is executed without error, the message fails.

> I did some investigations. It seems that the HTTPSToken for Client Certificate is correctly
evaluated by Neethi/CXF but some how get lost during the WSDL parsing. At the end all alternative
policies contain a transport binding (referencing a transport token) referencing a HTTPSToken
that requires Basic Authentication. I have attached a maven project that includes a simple
junit test. It uses the Camel test functionality (CamelSpringTestSupport) to send directly
a message to a CXF endpoint. mvn install or executing the junit test leads automatically to
the error described above.
> Best Regards,
> Jörg

This message was sent by Atlassian JIRA

View raw message