Re: 2way SSL errors - http conduit

[Glen Mazza]

This blog entry might help: 
http://www.jroller.com/gmazza/entry/cxf_x509_profile_secpol

Glen
On 03/09/2012 06:47 PM, Glen Mazza wrote:
What you have should work--does your namespace really start with 
"https://"; and not just "http://";?

Glen

On 03/09/2012 04:48 PM, jaybytez wrote:
One last question with regards to http:conduit:

I can only get the following to work with 2way SSL
<http:conduit name="*.http-conduit">

The documentation says to use the WSDL port with QName to make it 
specific
instead of "*":

<http:conduit name="{https://foo.com}FooPort.http-conduit";>

That doesn't seem to work for me...

&lt;service name="Foo">
&lt;port *name="FooPort"* binding="tns:FooPortBinding">
&lt;soap:address location="REPLACE_WITH_ACTUAL_URL"/>
&lt;/port>
&lt;/service>

Is the FooPort above the port name from the WSDL that is supposed to 
used in
http:conduit and just apply the targetNamespace?

--
View this message in context: 
http://cxf.547215.n5.nabble.com/CXF-2-4-Migration-removal-of-cxf-xml-2way-SSL-errors-tp5551465p5551804.html
Sent from the cxf-user mailing list archive at Nabble.com.




--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza