Newer versions of CXF use "org.apache.wss4j" for the crypto properties as
well as "security.*" for the security configuration. The
"org.apache.ws.security" configuration options as well as "ws-security.*"
are older. However both are supported in reasonably current versions of CXF.
Colm.
On Tue, F
Query, in the properties file referenced from the XML file, is this the right
prefix for the properties?
org.apache.ws.security.crypto.merlin.*
The reason I ask is, the GIT URL you sent me to, the entry keys begin with
"security.*" instead of "ws-security.*" I've seen else where; as well as bei
>
>
>
> http://schemas.xmlsoap.org/ws/2005/07/
> securitypolicy">
>
>
> xmlns:sp="http://sc
[mailto:cohei...@apache.org]
Sent: Monday, February 20, 2017 8:39 AM
To: users@cxf.apache.org
Subject: [EXTERNAL] Re: Problem calling WCF MS service with security, policies,
trust
For WS-SecureConversation, the configuration parameters for the "bootstrap"
phase end with ".sct".
: Colm O hEigeartaigh [mailto:cohei...@apache.org]
Sent: Monday, February 20, 2017 8:39 AM
To: users@cxf.apache.org
Subject: [EXTERNAL] Re: Problem calling WCF MS service with security, policies,
trust
For WS-SecureConversation, the configuration parameters for the "bootstrap"
phase end with
AM
To: users@cxf.apache.org
Subject: [EXTERNAL] Re: Problem calling WCF MS service with security, policies,
trust
For WS-SecureConversation, the configuration parameters for the "bootstrap"
phase end with ".sct". See the examples here:
https://git-wip-us.apache.org/repos/asf?p=cxf
For WS-SecureConversation, the configuration parameters for the "bootstrap"
phase end with ".sct". See the examples here:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=systests/ws-security-examples/src/test/resources/org/apache/cxf/systest/wssec/examples/secconv/client.xml;h=b5a395f70
My situation has two WSDLs: a and b.
Both use the same keystore which contains two Trusted Cert Entries and a
Private Key Entry (x.509 cert). This key is supposed to be used to sign and
encrypt the messages.
Calling the a::authentication.authenticate method should be over https, signed
and enc
he.org
Subject: [EXTERNAL] Re: Problem calling WCF MS service with security
Answer inline.
On Thu, Feb 16, 2017 at 2:02 PM, Morein, Arnie
wrote:
> And that is part of the confusion. What is meant by PORT NAME?
>
The Port name in the WSDL. For example, from the ws-security-examples, syste
I put the client-crypto.properties and jsk files in /WEB-INF/classes, and
updated the security.signature.properties in the XML file to point to
/WEB-INF/classes/xyz as appropriate.
CXF still cannot find it.
So I moved the client-crypto.properties, jks and new cxf.xml file to the jar
project wh
Answer inline.
On Thu, Feb 16, 2017 at 2:02 PM, Morein, Arnie
wrote:
> And that is part of the confusion. What is meant by PORT NAME?
>
The Port name in the WSDL. For example, from the ws-security-examples,
system tests:
http://www.example.org/contract/DoubleIt}DoubleItPlaintextPort";
created
And that is part of the confusion. What is meant by PORT NAME?
The Interface? I have tried:
{ http://aamva.org/authentication/3.1.0} IAuthenticationService
And the implementation (extends Service):
{ http://aamva.org/authentication/3.1.0} AuthenticationService
Neither matches. What else could
It looks like your jaxws:client "name" either does not match the WSDL port
or else the configuration file is not getting picked up at all. When you
have a security policy, you don't need to specify the "WSHandlerConstants"
style configuration. Take a look at the WS-Security Examples tests in the
"s
13 matches
Mail list logo
