Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Wed, 9 Oct 2013 14:12:42 +0000 (UTC)
From: "Joerg Kessler (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12673022.1381327852954.38493.1381327962957@arcas>
In-Reply-To: <JIRA.12673022.1381327852954@arcas>
References: <JIRA.12673022.1381327852954@arcas>
Subject: [jira] [Updated] (CXF-5325) error when having alternative transport
 bindings in WSDL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CXF-5325?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Kessler updated CXF-5325:
-------------------------------

    Attachment: cxf.client.test.sync.client.cert.junit.ext.zip

> error when having alternative transport bindings in WSDL
> --------------------------------------------------------
>
>                 Key: CXF-5325
>                 URL: https://issues.apache.org/jira/browse/CXF-5325
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Joerg Kessler
>             Fix For: 2.7.6
>
>         Attachments: cxf.client.test.sync.client.cert.junit.ext.zip
>
>
> Hi,
> we have received a WSDL from a WS provider that allows Basic Authenticati=
on or Client Certificate Authentication. When I configure Client Certificat=
e Authentication in the conduit for my CXF WS consumer. I receive the follo=
wing error
> WARNUNG: Interceptor for {http://xi.com/xiveri/source_runtime}ZMTOM_CXF_I=
N#{http://xi.com/xiveri/source_runtime}CXF_IN has thrown exception, unwindi=
ng now
> org.apache.cxf.ws.policy.PolicyException: Assertion of type {http://docs.=
oasis-open.org/ws-sx/ws-securitypolicy/200702}HttpsToken could not be asser=
ted: HttpBasicAuthentication is set, but not being used
> =09at org.apache.cxf.ws.security.policy.interceptors.HttpsTokenIntercepto=
rProvider$HttpsTokenOutInterceptor.assertHttps(HttpsTokenInterceptorProvide=
r.java:144)
> =09at org.apache.cxf.ws.security.policy.interceptors.HttpsTokenIntercepto=
rProvider$HttpsTokenOutInterceptor.handleMessage(HttpsTokenInterceptorProvi=
der.java:87)
> =09at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterce=
ptorChain.java:271)
> =09at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:541)
> =09at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:467)
> If I just allow Client Certificarte it works. If in the WSDL Client Certi=
ficate is defined first it works. If I use WSRM the Create Sequence is exec=
uted without error, the message fails.=20
> I did some investigations. It seems that the HTTPSToken for Client Certif=
icate is correctly evaluated by Neethi/CXF but some how get lost during the=
 WSDL parsing. At the end all alternative policies contain a transport bind=
ing (referencing a transport token) referencing a HTTPSToken that requires =
Basic Authentication. I have attached a maven project that includes a simpl=
e 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=C3=B6rg


--
This message was sent by Atlassian JIRA
(v6.1#6144)