The STS uses an interface which is in the cxf-rt-ws-security module:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=tree;f=rt/ws/security/src/main/java/org/apache/cxf/ws/security/sts/provider;h=853c9298b6a097de3ecc25707b618450289697b5;hb=HEAD
The implementation is available here:
Hello!
In my cxf client I need to use some GOST-based provider (namely CryptoPro
JCP) that uses non file-based (but directory-based) keystore type. How
should I configure it in trustManagers/keyStore element of Spring
configuration xml?
--
View this message in context:
Answers inline.
On Fri, Jul 10, 2015 at 8:14 PM, stephen.ctr.chapp...@faa.gov wrote:
WSSConfig doesn’t have that flag anymore as far as I can tell. Is this
default behavior now, or is there some other way to enable that behavior? I
see that I can set it on a RequestData, but I don’t have one
Hi Ellen,
The issue appears to be that CXF does not register optional policies on the
server side. As you have only one policy, this means that no valid policy
is registered and hence the AssertionInfoMap Object is null. This looks
like a bug in CXF to me, but I'm not sure what the impact of
--
John Baker, Web Technologies Consultant.
http://www.javasystemsolutions.com
+44 77 3639 3822
On Mon, Jul 13, 2015, at 11:33 AM, users-h...@cxf.apache.org wrote:
Hi! This is the ezmlm program. I'm managing the
users@cxf.apache.org mailing list.
I'm working for my owner, who can be
hi There,
I am writing a dynamic CXF client using JaxWsDynamicClientFactory and
parsing a wsdl . Unfortunately the wsdl is generting an exception
* A class/interface with the same name mu.mcb.cbk.ArrayOfUserInfo is
already in use. Use a class customization to resolve this conflict.*
in
Thanx, Colm. There's a few more things that have migrated somewhere that I'm
having trouble finding ...
1. WSSecurityUtil used to have some DOM methods that mostly look like they were
moved to XMLUtils. But there's one I can't find - storeElementInContext. Is
that one still around, or will I
Hi Christian,
thanks for your fast reply. The example on the Felix webpage is a bit outdated
and the http bridge (version 2.3.2) in its manifest has now
Import-Package: javax.servlet;version=[3.0,4),javax.servlet.descriptor
;version=[3.0,4),javax.servlet.http;version=[3.0,4)
So what we have
Hi Thomas,
I think this fix is not correct. If the http service can only be found
with .open(true) it means that the package the service implements and
the package cxf imports are different.
I assume you simply forgot one step of the bridge installation guide:
1. WSSecurityUtil used to have some DOM methods that mostly look like they
were moved to XMLUtils. But there's one I can't find -
storeElementInContext. Is that one still around, or will I need to
implement locally?
The functionality is now implement in WSDocInfo instead. See
Hi everyone,
I am having some problems with CXF HTTP Transport in an OSGi environment using
Apache Felix as OSGi Framwork.
I'm using the Felix Http Bridge to start Felix within a .war web application
which runs in Tomcat. The problem is, that the ServiceTracker which is set up
in
It's not possible right now to use non file-based keystores with the CXF
KeyManagers/TrustManagers spring TLS configuration. You'll have to
configure TLS in code via TLSClientParameters.
Colm.
On Mon, Jul 13, 2015 at 11:41 AM, est412 est...@gmail.com wrote:
Hello!
In my cxf client I need to
Thank you for clarification!
--
View this message in context:
http://cxf.547215.n5.nabble.com/Non-file-based-keystore-and-Spring-configuration-tp5759089p5759114.html
Sent from the cxf-user mailing list archive at Nabble.com.
13 matches
Mail list logo
