I have been trying for more than a week to get a ws-security cxf-proxy
setup based on Camel 3.8 and Java 8.
Cxf is using policy based approach.
The error is :
Could not find conduit initiator for address:
jaxws:bean:realWebServiceClient and transport:
http://schemas.xmlsoap.org/soap
0.75
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: zondag 17 mei 2015 8:16
To: users@camel.apache.org
Subject: Re: camel spring-ws component with ws-security (username and password)
Hi
It looks as if org.springframework.util.backoff.BackOff is part of Spring 4
Hi
It looks as if org.springframework.util.backoff.BackOff is part of
Spring 4.1.x onwards. So you can try upgrade Spring.
On Fri, May 15, 2015 at 5:41 PM, Ronny Aerts wrote:
> Hello camel community,
>
> Does anyone of you have some knowledge/experience using ws-security with the
Hello camel community,
Does anyone of you have some knowledge/experience using ws-security with the
camel spring-ws component?
I want to a Security tag with username and password to the soap header but this
does not work for me.
I found website
http://docs.spring.io/spring-ws/site/reference
You're mixing up two different ways of configuring WS-Security in CXF. When
you have a security policy, you don't need to add the WSS4JOutInterceptor
explicitly, CXF will take care of doing this for you. Instead you need to
supply some contextual properties to enable it to fulfil the
Can anybody help please?
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-invoking-WS-Security-Enabled-net-service-using-cxf-endpoint-org-apache-cxf-interceptor-Fault-Ne-tp5761081p5761096.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I am trying to invoke a third party .net web service with ws-security and I
am getting the following exception inspite of configuring all the required
parameters in WSS4JOutInterceptor. Been struggling with this issue for past
one week. Appreciate any help.
*org.apache.cxf.interceptor.Fault: No
to github account @
> https://github.com/garethahealy/jboss-fuse-examples - ws-security-*
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/CXF-with-WS-Security-using-JAAS-tp5758345p5758447.html
> Sent from the Camel - Users mailing list archive a
I've also added the code my to github account @
https://github.com/garethahealy/jboss-fuse-examples - ws-security-*
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-with-WS-Security-using-JAAS-tp5758345p5758447.html
Sent from the Camel - Users mailing list archi
:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">y2rUhVaSPSYGGJxx5vz/gAe8Kxo=</wsse:Password>;
<wsse:Nonce
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu
Camel
headers which cause problems downstream.
Thanks,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/ws-security-tp5753430p5753649.html
Sent from the Camel - Users mailing list archive at Nabble.com.
My impression was that cxf was supported to remove the headers
automatically when it processed them. Switching everything to POJO doesnt
solve the problem. The proxied service still recieves the WS-Security
headers (even though they were already taken care of my the proxy). This is
the output
If you switch the data format to POJO, you should not see the security header
any more.
If you still need to use PAYLOAD data format, you need to clean up the soap
header of the payload message, as camel-cxf doesn’t put the soap header into
camel message header.
--
Willem Jiang
Red Hat, Inc.
I am attempting to proxy calls to a service and centralize ws-secuity
handling within a camel route. Everything works perfectly but the
ws-secuirty headers arent being removed and are instead being propogated
down to the proxied service. This results in a MustUnderstand problem as
the proxied servi
hanks!
Jin
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749361.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t; =out=
>
> > class="org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor">
>
>
>
>
> > value="com.sms.dcp.KeystorePasswordCallback" />
>
>
>
> > value="cms-files/cms-trusted-crypto-PDT.properties" />
uot;{http://vbms.vba/external/eDocumentService}*"; />
http://cmp.vba/cmp}*";
value="{http://vbms.vba/cdm}*"; />
but it didn't have any effect on the outgoing request.
--
View this message in
this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749312.html
Sent from the Camel - Users mailing list archive at Nabble.com.
em? If it has the
> SOAPMessage, shouldn't that be enough?
>
> Thanks!
> Jin
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749309.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
rceptor.java:788)[162:org.apache.cxf.cxf-rt-ws-security:2.7.7]
> at
> org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:336)[162:org.apache.cxf.cxf-rt-ws-security:2.7.7]
> at
> org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessag
Willem - Understand that Camel will not copy the in headers to out headers.
But the real question is: Does CXF endpoint really need them? If it has the
SOAPMessage, shouldn't that be enough?
Thanks!
Jin
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-wi
:org.apache.cxf.cxf-rt-ws-security:2.7.7]
at
org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:336)[162:org.apache.cxf.cxf-rt-ws-security:2.7.7]
at
org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:95)[162
ciate your feedback.
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749304.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749306.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749305.html
Sent from the Camel - Users mailing list archive at Nabble.com.
string and rightfully
construct the SOAPMessage.
Appreciate your feedback.
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749304.html
Sent from the Camel - Users mailing list archive at Nabble.com.
//camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749283.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Jin
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749280.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
I did get a fault response saying the body element is NULL from soapUI
> mockup service.
>
> I will check the WSDL and share anything if useful.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp57
espace.
> I wonder if anything that needs to done to the camel message header.
>
> Is there an easier/right way to generate a request to a cxf component that
> accepts CXF_MESSAGE?
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabb
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749284.html
Sent from the Camel - Users mailing list archive at Nabble.com.
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749283.html
Sent from the Camel - Users mailing list archive at Nabble.com.
will check the WSDL and share anything if useful.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749282.html
Sent from the Camel - Users mailing list archive at Nabble.com.
sdl of the service you are trying to call. Under
operations, please check if there is any schema defined for "out" element
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749281.html
Sent from the Camel - Users mai
.
Can some expert help out here?
Thanks,
Jin
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749280.html
Sent from the Camel - Users mailing list archive at Nabble.com.
MESSAGE?
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749256.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749256.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ew this message in context:
> http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749229.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
65427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749229.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749228.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thanks for the quick reply. That's a good clue. Can you give me something
more concrete?
What would route look like?
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749226.html
Sent from the Camel - Users mailing
Did u try using xslt after the processor bean part is over ?
On 22 Mar 2014 09:21, "chaij" wrote:
> I am writing a SOAP proxy. When a SOAP service call comes in, it goes to a
> CXF consumer->Processor->CXF producer (with WS-Security)
>
> Since the incoming service c
I am writing a SOAP proxy. When a SOAP service call comes in, it goes to a
CXF consumer->Processor->CXF producer (with WS-Security)
Since the incoming service call and the outgoing service call are from
different wsdl and thus different namespace, I would need to transform the
informatio
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Mon, Sep 9, 2013 at 5:17 PM, gliesian wrote:
> Hi,
>
> I'd like to do some WS-Security (e.g., wsse
Hi,
I'd like to do some WS-Security (e.g., wsse) testing with Camel...
Is camel a good tool to use for this sort of testing...
If so, where do I start my path, and what resources are available to support
this space?
Thanks,
Robert
--
View this message in context:
http://camel.4654
-cxf pretty much keeps everything as a stream and
>> > > bypasses much of the CXF interceptor chain and conversions and such. In
>> > > some cases, that's very good. Performance and stuff works well. However,
>> > > it also means a lot of CXF's processin
l-cxf pretty much keeps everything as a stream and
> > > bypasses much of the CXF interceptor chain and conversions and such. In
> > > some cases, that's very good. Performance and stuff works well. However,
> > > it also means a lot of CXF's processin
CXF's processing capabilities are not used/usable.
>>
>> If you flip to PAYLOAD mode or the new CXF_MESSAGE mode, it will likely
>> work find for you. Those will behave more like normal CXF clients/servers
>> that would allow all the ws-security stuff to work.
>&g
flip to PAYLOAD mode or the new CXF_MESSAGE mode, it will likely
> work find for you. Those will behave more like normal CXF clients/servers
> that would allow all the ws-security stuff to work.
>
> Dan
>
>
>
> On Nov 20, 2012, at 10:01 AM, Jesper Nygårds
> wrote:
>
> &g
e not used/usable.
If you flip to PAYLOAD mode or the new CXF_MESSAGE mode, it will likely work
find for you. Those will behave more like normal CXF clients/servers that
would allow all the ws-security stuff to work.
Dan
On Nov 20, 2012, at 10:01 AM, Jesper Nygårds wrote:
> I have a scenario
I have a scenario where I want to add wss signing to an outgoing web
service call. I am trying to accomplish this by using a cxf consumer and a
cxf producer wired together by camel as a simple proxy.
The idea is this: a system sends an un-signed SOAP request to our CXF web
service requiring no sec
e it , you need to remove the header yourself
just like this
from(cxf:xxx).removeHeader("org.apache.cxf.headers.Header.list").xxx
or configure a customer HeaderFilterStrategy to filter the SOAP headers.
On 6/14/11 12:43 PM, ext2 wrote:
> Thanks Willem
> It's the WS-Sec
Thanks Willem
It's the WS-Security header;
//soap 12
QName wsseQName = new QName(WSConstants.WSSE_NS, WSConstants.WSSE_LN);
//soap 11
QName wsse11QName = new QName(WSConstants.WSSE11_NS, WSConstants.WSSE_LN);
When security is enabled, we filter it. Then everything is ok.
> -
Thanks Willem
It's the WS-Security header;
//soap 12
QName wsseQName = new QName(WSConstants.WSSE_NS, WSConstants.WSSE_LN);
//soap 11
QName wsse11QName = new QName(WSConstants.WSSE11_NS, WSConstants.WSSE_LN);
When security is enabled, we filter it. Then everything is ok.
> -
What's request security header name ?
Maybe we can consider to filter the security header of the CXF message
in CxfHeaderFilterStrategy.
You can configure your own HeaderFilterStrategy by extends the
CxfHeaderFilterStrategy.
On 6/14/11 10:37 AM, ext2 wrote:
Hi:
Following is a simpl
Hi:
Following is a simple sayHello Webservice implemented by camel.
The webservice's request is configured to decrypt by server
certificate and response is configured to encrypt by client certificate.
If I use a bean as following, every thing is ok
On 6/11/11 5:56 PM, Claus Ibsen wrote:
On Fri, Jun 10, 2011 at 9:36 AM, Willem Jiang wrote:
> Hi Mark,
>
> I'm afraid you can just configure the WSS4jInInterceptor through the
> cxf:bean:xxx , current camel-cxf doesn't support to configure it through
> URI.
>
Willem what would it take to s
cxf:bean:cxfEndpoint
>> endpoint definition?
>>
>> Thanks,
>> Mark
>>
>> Mark Borner
>> Java Developer - ZStream Xpress
>>
>>
>> From: Charles Moulliard
>> To: users@camel.apache.org
>> Date: 10/06/2011 04:23 PM
>&
x27;m
using cxf://someAddress[?options] instead of the cxf:bean:cxfEndpoint
endpoint definition?
Thanks,
Mark
Mark Borner
Java Developer - ZStream Xpress
From: Charles Moulliard
To: users@camel.apache.org
Date: 10/06/2011 04:23 PM
Subject:Re: Camel CX
ache.org
> Date: 10/06/2011 04:23 PM Subject: Re: Camel CXF & WS-Security
> --
>
>
>
> Hi Mark,
>
> I have created one year an example in camel project available here :
>
>
> https://github.com/gnodet/camel/tree/trunk/examples/camel-exa
e.org
Date:
10/06/2011 04:23 PM
Subject:
Re: Camel CXF & WS-Security
Hi Mark,
I have created one year an example in camel project available here :
https://github.com/gnodet/camel/tree/trunk/examples/camel-example-reportincident-ws-security-osgi
Regards,
Charles Moulliard
Apache Commit
Hi Mark,
I have created one year an example in camel project available here :
https://github.com/gnodet/camel/tree/trunk/examples/camel-example-reportincident-ws-security-osgi
Regards,
Charles Moulliard
Apache Committer
Blog : http://cmoulliard.blogspot.com
Twitter : http://twitter.com
Does anyone have any examples of how to configure a Camel CXF endpoint to
use WS-Security? I need to secure an outbound and inbound SOAP message.
Thanks,
Mark
Mark Borner
Java Developer - ZStream Xpress
This email is intended for the named recipient only. It may contain
information
63 matches
Mail list logo
