Should the wsdl basically look like this?
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;>...
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;>...
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;>...
Thanks Colm! I was able to solve my issues using your suggestion, I basically
load the properties java object instead of secifying the url to the props
file.
ctx.put(SecurityConstants.ENCRYPT_PROPERTIES,
Hey all,cxf-bundle- 2.7.15wss4j - 1.6.18I observed something in the soap
message that its security header contains multiple entries for things like
Signature, Timestamp, EncryptedKey etc as shown below. I have basically
generated java sources using wsdl2java and the wsdl lives here:
Not sure exactly which class you want me to pass the crypto properties object
to?
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
Yes I tried the full path and it won't work. The reason being the same, the
AbstractBindingBuilder.getCrypto method tries to load it from the classpath.
If it doesn't find it then it throws a PolicyException.
I cannot upgrade to cxf latest versions unfortunately.
It looks like I could use a
Colm,
I used your suggestion and solved my problem. But I m running into a similar
problem elsewhere where the resource file is not found by the
AbstractBindingBuilder class. Here is the exception:
WARN [2017-10-20 12:56:45,022] org.apache.cxf.phase.PhaseInterceptorChain:
Interceptor for
Colm,
For the workaround- can you show me the diff of your fix? Are you basically
loading the resource in a different way rather than the classloader way? If
you show me what the diff is for the fix you put in then I will use that as
the base.
Again thanks for fixing and for the quick
i know this was long time ago but I just wanted to check if you were able to
solve this issue.
You mention ResourceResolver. What would that solution look like? Can you
please explain?
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
Colm, that's great! Can you please let me know when this would be available
for use? Will it be made available via maven? Is it a wss4j 1.6.19 fix?
Unfortunately, I cannot upgrade to the latest versions of cxf because we
support sdk code given to us which was written a long time ago.
Much
Is there a way of using this technique described in to load 2 different
keystores rather than just 1? Construct Properties object in-memory, and
have CXF use that instead.
package soap.common.interceptors;
import client.clientmgr.ClientInfo;
import
Colm,
thanks for responding.
It's hard for me to create a test-case because there is so many things
involved. I did my best below:
Client creates a file called client.properties under */tmp* which looks like
this:
sign.propFile=client/100/sign.properties
Environment:
cxf-bundle: 2.7.18
wss4j: 1.6.19
I am trying to act as a soap client and send a soap message which is both
signed and encrypted. For signing and encrypting, different keystores are used.
My own private key for signing and a server's public certificate for encrypting
the soap
Environment:
cxf-bundle: 2.7.18
org.apache.ws.security.wss4j: 1.6.19
I am trying to act as a soap client and send a soap message which is both
signed and encrypted. For signing and encrypting, different keystores are
used. My own private key for signing and a server's public certificate for
13 matches
Mail list logo
