My question here is, if STS endpoint need to support more than one
encryptionAlgorithm and keyWrapAlgorithm, how do we satisfy that?
The values specified as part of the EncryptionProperties bean are just
default values. The STS client can also specify other algorithms to use by
sending a
Hi Sergey and Josef,
in Kerberos there are two kinds of tickets. The Ticket Granting Ticket
(TGT) together with a session key is the one issued for the user after
he authenticates on his machine. This ticket then allows to get a
Service Ticket (ST) for a certain server. This service ticket is
First off, apologies for the spam. I thought this would be of benefit to some
of the users on this mailing list. We recently released v1.0 of our flagship
product, Examine, a comprehensive web services testing tool with excellent SOAP
and REST testing support. Unlike other testing
tools,
URL please... (And don't forget to post on the Metro and Jersey users'
lists also.)
Glen
On 07/18/2012 07:28 AM, Murali Krishnan wrote:
First off, apologies for the spam. I thought this would be of benefit to some
of the users on this mailing list. We recently released v1.0 of our flagship
Hi Christian, All
On 18/07/12 10:06, Christian Schneider wrote:
Hi Sergey and Josef,
in Kerberos there are two kinds of tickets. The Ticket Granting Ticket
(TGT) together with a session key is the one issued for the user after
he authenticates on his machine. This ticket then allows to get a
Hi Colum,
As always, thanks for your response. As you can tell, I don't have much
knowledge about encryption algorithms, so I have following questions.
What JDK vendor and version are you using on the WSP side? Some JDK's
have
a problem with the rsa-oaep key wrapping algorithm. Try just using
Hi Colm,
Actually setting keyWrapAlgorithm to
http://www.w3.org/2001/04/xmlenc#rsa-1_5; didn't work. I forgot to restart
Tomcat after I made changes. My apologies. At this point, I have to comment
out encryptionProperties to get this work.
Thanks.
Gina
On Wed, Jul 18, 2012 at 8:11 AM, Gina
On 18/07/12 13:05, Sergey Beryozkin wrote:
Hi Christian, All
On 18/07/12 10:06, Christian Schneider wrote:
Hi Sergey and Josef,
in Kerberos there are two kinds of tickets. The Ticket Granting Ticket
(TGT) together with a session key is the one issued for the user after
he authenticates on his
So, does it mean that WSP keyWrapalgorithm depends on JDK vendor and
version?
No it should work for both. There are some workarounds for certain JDK's
that use RSA-OAEP in both WSS4J and Santuario though - perhaps you've hit a
use-case that doesn't work. I can't reproduce the problem though.
Hi Glen,
Thanks, will do. Not sure if the links in the message earlier got filtered
out. But this is the URL for the complete list of features and download.
http://www.stratumsoft.com/examine-features/
http://www.stratumsoft.com/download/
Examine uses CXF as part of its underlying stack and is
Thanks Mark..
It's working now.. Some of the Schema/XSD are missed in local.
Regards,
Ganesh
--
View this message in context:
http://cxf.547215.n5.nabble.com/WSDLException-faultCode-PARSER-ERROR-Connection-reset-tp5711085p5711241.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi Colm,
What error are you seeing? The default value is rsa-1_5 so it shouldn't
make any difference whether it's specified or not.
No doubt that rsa01_5 is default value. When I comment out
encryptionProperties, client sends following SOAP request to WSP. I
abbreviated some part of request to
Are you sure you're using the ut_encrypted port? Because the token that is
issued by the STS is encrypted for the WSP and so should appear in the WSC
- WSP request as an EncryptedData structure, whereas in your test-case I
can see the SAML Assertion.
Colm.
On Wed, Jul 18, 2012 at 2:50 PM, Gina
Hi Sergey,
In my case the endpoint is a simple jaxws:client specified in the Spring
app-context and injected to a few Controllers or similar classes.
The only extra thing is that we want to 'impersonate' or 'delegate' the user's
credentials so that any call we do from the Web Service client
Previous logs obtained when I set EncryptionProperties as follow. This is
same as default value when I comment EncryptionProperties out. I don't
know why it doesn't work.
bean id=encProperties
class=org.apache.cxf.sts.service.EncryptionProperties
property name=encryptionAlgorithm
Hi Josef
On 18/07/12 15:47, Josef Bajada wrote:
Hi Sergey,
In my case the endpoint is a simplejaxws:client specified in the Spring
app-context and injected to a few Controllers or similar classes.
The only extra thing is that we want to 'impersonate' or 'delegate' the user's
credentials so
By the way, SpnegoAuthSupplier now checks for GSSCredential on the CXF
message and will use it if it is there to get a new token - that might
simplify a bit the propagation in the future for cases when no CXF is
involved to get the original in request
Sergey
On 18/07/12 17:10, Sergey
Hi Sergey,
Thanks for that!
So, if we manage to get access to the GSSCredential object, how would we add it
to the request being made so that the SpnegoAuthSupplier finds it?
What method calls do we need to do to the CXF Jax-ws client injected by spring
so that we add the GSSCredential object?
Hi Colm,
I did some debugging work on both WSP and STS side.
1. WSP Side
I did debugging when commenting out EncryptionProperties and uncommenting
it on STS side, but I don't see any differences.
2. STS Side.
I found out settings for both encryptionAlgorithm and keyWrapAlgorithm
doesn't affect
Hello Willem, hello Scott!
Thanks for your reply and apologies for my late reply.
If I provide a Camel proxy service which also leverage on the HTTP OSGI
service, than the new proxy service, the service for customer A and the
service for customer B are available on all ports (if we assume each
Hi,
On 18/07/12 19:44, Josef Bajada wrote:
Hi Sergey,
Thanks for that!
So, if we manage to get access to the GSSCredential object, how would we add it
to the request being made so that the SpnegoAuthSupplier finds it?
What method calls do we need to do to the CXF Jax-ws client injected by
Good day,
I have been able to move forward, but things aren't making sense to me. I
would appreciate any help in understanding what's going on or where to look
next.
I have deployed my war file to Tomcat 6.0.32, but I'm getting exceptions
that I need to put the jetty jars on the
Maybe my blog article would help:
http://www.jroller.com/gmazza/entry/web_service_tutorial
You might wish to rename your cxf-servlet.xml (cxf-beans.xml or anything
else will be fine)--that's a special name reserved when you're not using
the contextConfigLocation parameter in the web.xml,
23 matches
Mail list logo
