Hi Andrei, Sergei,
thanks for your help. this has cleared things up for me. I implemented
client-cert authentication (via http) using the cxf http transport and it
works a treat. within the service implementation i can access the current
user via the annotation.
thanks again.
Michael
--
View th
Anyways, I got it working through loading my context beans thru CXFServlet
init-param instead of the Spring's ContextLoaderListener.
-Sonam
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Friday, April 04, 2014 4:36 AM
To: users@cxf.apache.org
Subject: Re:
Hi, sorry for a delay
On 03/04/14 22:29, Aysun Bascetincelik wrote:
(Sorry for the earlier accidental post)
Hello,
I'm having some issues with the WebClient provided with CXF 2.7.8. We're
using the below code to connect to a web service through SSL and non-SSL
but my question is mostly concer
There seems to be a conflict between Jersey and CXF implementations...
Basically, if you'd like to use 2.0 API you need to avoid having 1.1 API
and implementations loaded, especially in non-OSGI containers.
As I said CXF does the best effort to work alongside other JAX-RS API
and implementations
Hi,
Like Sergei already answered
(http://cxf.547215.n5.nabble.com/Fwd-Re-utilizing-tomcat-authentication-for-webservices-tc5742379.html
) , there are two different authentication approaches for SOAP web services:
1. Protocol based (HTTP Basic, Digest, Client-cert)
2. SOAP WS-Security based (User
hi,
i think i've made some progress.
found the following docs:
https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport%28includingSSLsupport%29-BasicAuthentication
looks like the conduit is the way to go. Added the following to my client
call:
HTTPConduit
