I was surprised to see the following in cxf-transport.xml:
util:list id=transportEndpoints
value.*/value
valuehttps://localhost:(\d)*/doubleit/services/doubleittransport.*/value
/util:list
I thought doubleit was just used for examples - should this be present in a
production STS?
Many thanks,
Hello,
I am working on the right way to configure Client Timeout on client side
and I am kind of confused by what I read:
-
http://cxf.547215.n5.nabble.com/Setting-Http-conduit-using-spring-configuration-file-td2644363.html
- https://issues.apache.org/jira/browse/CXF-3011
-
AFAIK, this is what createdFromAPI or abstract attributes can help
with (they are effective for jaxws:client), something I've started
looking into recently too in context the of JAX-RS client runtime work
Sergey
On 03/05/13 01:14, Jason Pell wrote:
I guess i should have been clearer. If i
Well, it is not possible to register more than one service using DOSGi
using the same org.apache.cxf.rs.httpservice.context. I updated CXF to
2.7.4 and DOSGi to 1.4.0 and now I'm using
org.apache.cxf.rs.httpservice.context
property with full relative address and org.apache.cxf.rs.address / in
all
Hi,
Private key is password protected in the java keystore.
CXF needs private key for the signature, therefore password should be provided
using PasswordCallback for each alias.
Regards,
Andrei.
-Original Message-
From: cvm [mailto:chetan.v.minaj...@jpmorgan.com]
Sent: Donnerstag,
Hi
On 03/05/13 10:53, Julio Carlos Barrera Juez wrote:
Well, it is not possible to register more than one service using DOSGi
using the same org.apache.cxf.rs.httpservice.context. I updated CXF to
2.7.4 and DOSGi to 1.4.0 and now I'm using
org.apache.cxf.rs.httpservice.context
property with full
Hi,
If I am not mistaken, STS communication is triggered by policy IssuedToken
assertion.
Your policy specifies SymmetricBinding using X509 protection token and
UsernameToken as SignedEncryptedSupportingTokens.
I do not think that your policy will initiate communication with STS service at
The Symmetric key that the client generates signs (and encrypts) the
request (SOAP Body). There is no need for a signing certificate as you are
using the Symmetric binding. Authentication is enforced via the
UsernameToken SupportingToken.
Colm.
On Fri, May 3, 2013 at 4:25 AM, Josh Hill
I'm trying to understand the key and keystore requirements for fediz using
IDP, STS and RP all deployed in separate web containers and using native
spring security in the RP.
I have uploaded my current understanding here:
I'm trying to understand the key and keystore requirements for fediz using
IDP, STS and RP all deployed in separate web containers and using native
spring security in the RP.
I have uploaded my current understanding here:
http://picpaste.com/Fediz_Keystores-INNrABZM.png
Questions:
Is this
Hello All,
Im trying to depoly a WAR file in karaf 2.3.1 but im getting the below
exception.. The WAR file is placed under the deploy folder.
karaf@root osgi:install -s
webbundle:camel-example-servlet-tomcat-2.10.4.war?Bu
Hi,
Could you also post the exception in log when deploy the war failed?
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Great overview. Would be great to have something like this on the wiki. I
spotted one thing. The public key in the RP is the STS App Public Key instead
of STS Container SSL Public Key.
The keystore to validate the SAML token signature is configured here:
HI Yue,
I want my interceptor to be called before my serviceimpl but with
phase.Invoke the behavior looks different it is getting called after the
serviceimpl call.
Thanks,
remo.
--
View this message in context:
Hi all,
We are trying to co-exist jbossws (on jboss-4.2.3GA) and Apache CXF 2.6.1.
The problem is arising when we keep the jbossws-native-saaj.jar in the
jboss/lib/endorsed folder ,the SOAPMessage.class when it is trying to
resolve the implemetor ,it is taking from jbossws-native-saaj.jar instead
Here is the stack trace:
2013-05-03 07:00:14,136 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS]
SOAP request exception
java.lang.ClassCastException:
com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl
at
Hi,
Were you able to find a solution for your problem.We are kind of stuck at
the same problem
Saludos
Kartheek
-
Saludos
Kartheek
--
View this message in context:
http://cxf.547215.n5.nabble.com/Unable-to-create-message-factory-for-SOAP-tp550508p5727146.html
Sent from the cxf-user
JBoss AS 4.2.3 was released on July *2008*, it's probably time to move
to something recent...
The exception you're getting basically says that the jbossws-native
jaxws impl is not able to work with the saaj-ri (as it was meant to run
with its own jbossws-native-saaj instead). Depending on what
Thanks Alessio. None of the versions we can change now per the client
requirements but can you please tell if there is a way to instruct CXF to
use it's own saaj implementation (sun) and Jbossws to use it's own native
libraries?
What you have detailed is correct,it is coming because the endorsed
As Alessio mentioned….. CXF isn't even in that stack trace you provided.
You're not even ending up using CXF at all. If the intention is to be using
CXF, that's the first issue you need to resolve.
That said, most likely you can remove the SAAJ impl and saaj-api jars we
provide and use
Hi Oli,
Thanks for checking over the image. Happy for the image to be uploaded to
the wiki. I have the Visio document it came from too if that helps.
As for the option for IDP to STS authentication using
SignedSupportingTokens or mutual SSL-handshake, I'm not sure yet. At this
stage, I'm
Thanks for removing Colm - I just noticed there is still a reference to:
property name=issuer value=DoubleItSTSIssuer /
Is that required still?
On Fri, May 3, 2013 at 1:37 PM, Colm O hEigeartaigh cohei...@apache.orgwrote:
It's a service endpoint that CXF uses for testing. And no, it should
On May 3, 2013, at 10:45 AM, remo408 prav...@gmail.com wrote:
HI Yue,
I want my interceptor to be called before my serviceimpl but with
phase.Invoke the behavior looks different it is getting called after the
serviceimpl call.
The call into the service is done by an interceptor that runs
Hi, I'm in the process of updating my Jersey/CXF samples blog article
(http://www.jroller.com/gmazza/entry/jersey_samples_on_cxf) from CXF
2.6.2 to CXF 2.7.4. 11 of the 15 samples work OOTB with no problem.
One sample, Moxy
(https://github.com/gmazza/jersey-samples-on-cxf/tree/master/moxy,
Hi All:
I'm using an STSClient configured from spring XML. I have put the
BindingProvider.ENDPOINT_ADDRESS_PROPERTY into the requestContext of the
STSClient, and confirmed it sets this on the ClientImpl (in the
debugger), but it seems this is not enough to change the actual URL used
in the
Setting BindingProvider.ENDPOINT_ADDRESS_PROPERTY as shown here might
work for you: http://www.jroller.com/gmazza/entry/soap_client_tutorial
Glen
On 05/03/2013 01:22 PM, David Mansfield wrote:
Hi All:
I'm using an STSClient configured from spring XML. I have put the
A similar problem occurs with https-server-glassfish example
(https://github.com/gmazza/jersey-samples-on-cxf/tree/master/https-server-glassfish)
in upgrading from CXF 2.6.7 to CXF 2.7.4 on latest Glassfish Server
3.1.2.2 following instructions given in README:
Got the thing I guess...JBossWs is the problem with CXF . when we removed the
jbossws.sar and jbossws.deployer, this security configuration is working
fine.
Can we do something to remove this conflict.
Nidhi
--
View this message in context:
Hi,
Unfortunately, I have to call a service that uses the older rpc/encoded SOAP
binding.
When I try to create the clients I've got the following error:
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -validate -client -verbose campinas_dsf.wsdl
wsdl2java - Apache
http://www.hark.com/clips/mhsfrzhzky-here-i-come-to-save-the-dayhttp://www.jroller.com/gmazza/entry/calling_rpc_encoded_web_services
: http://www.jroller.com/gmazza/entry/calling_rpc_encoded_web_services
HTH,
Glen
On 05/03/2013 02:41 PM, Fernando Silva wrote:
Hi,
Unfortunately, I have
In the STS stsstore.jks, the myidpkey is imported:
keytool -import -trustcacerts -keystore stsstore.jks -storepass stsspass
-alias myidpkey -file MyIDP.cer -noprompt
How does the code know how to use this keystore and certificate for
verifying the UsernameToken in the requests?
The following
Hi Glen
Nice to see you working on updating the examples, thanks for that.
Please try 2.7.5-SNAPSHOT, this issue should disappear, I updated the
client and server runtime to protect itself from multiple
RuntimeDelegates floating around, so the foreign JAX-RS Responses are
copied to CXF
Hi Sergey, I republished the blog entry today:
http://www.jroller.com/gmazza/entry/jersey_samples_on_cxf, MOXy now
works after I upgraded to 2.7.5-SNAPSHOT, but three samples are still
stuck at 2.6.7:
https-server-glassfish
You should define a http conduit and you can use a wild card in the id of
the conduit to make sure it applies to your service.
To ensure it applies to every service you can set a name *.http-conduit
Because the config of the conduit will be applied at init time its ok no
issues with thread
Sergey,
Thanks for reply. I had a look at the docs (but not the code as yet) and
createdFromAPI seems to be for when you have a pre-existing generated
client already instatiated as a bean with a specific bean id.
Although certainly is going to be a good starting point, what i was hoping
for is a
35 matches
Mail list logo
