Hi All,
I am using axis21.6.0 with rampart. My policy.xml has the details of the
client provided keystore provided below. I am getting the exception
"org.apache.xml.security.signature.XMLSignatureException: Supplied key
(sun.security.provider.DSAPrivateKey) is not a RSAPrivateKey instance".
(detai
Hi,
Thanks for your email. My WSDL is not java based and does not have the
security header information.
I have the keystore details to connect to my webservice.
I am able to consume the webservice through SOAP UI by configuring the SSL
info or the keystore details.
However I am using axis2's WSDL
Quick question in relation with this. It is possible to change the
namespace of the objected passed as arguments to the webservices? Because
we have the following service.xml:
http://zzz.yyy.xxx";>
Book sample service
http://zzz.yyy.xxx/xsd"; />
o
Hi,
On Fri, Apr 20, 2012 at 12:14 AM, Philippe A. wrote:
> Hello,
>
> Can someone explain the purpose of the targetNamespace attribute in
> services.xml?
>
> My webservice namespace appears to be actually set by the ServiceClass
> parameter "project.webservices.svc.Class". If I set targetNamespa
Same result in 1.6.1. sp:EncryptBeforeSigning seems to be broken.
I think the problem lies on the client side, because I have the same result
whether or not the server uses the same protection order. In other words,
the server always reject client "encrypted first" request. If the client
signs fir
I only wish the list would be a bit busier. I didn't see a whole lot of
feedback since I started posting.
2012/4/25 Sagara Gunathunga
>
>
> On Wed, Apr 25, 2012 at 8:43 PM, Philippe A. wrote:
>
>> It is not unusual to post on the mailing list before reporting a bug. Who
>> knows, I could get s
I am not trying to say do not post on the mailing lists of course, but looking
at what he had quoted below, a page full of conflicting info about supported
standards, it is obvious it is a bug and deserves a JIRA to be fixed.
From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com]
Sent: We
On Wed, Apr 25, 2012 at 8:43 PM, Philippe A. wrote:
> It is not unusual to post on the mailing list before reporting a bug. Who
> knows, I could get some feedback. .
>
+1 Philippe.
It always best practice to contact use list first if you not clear about
the issue because user list is dedicate
It is not unusual to post on the mailing list before reporting a bug. Who
knows, I could get some feedback. .
2012/4/18 George Stanchev
> Either way it is nice to submit a JIRAs, for encountered issues or for ENH
> requests, this way it has a chance of being addressed…
>
> ** **
>
> *From:*
I am not doing that myself but I would expect common scenarios should work
fine. What matters are the features used by the server and features
supported by the client. The client is only concerned with the wsdl.
2012/4/24 Natanasabai C
> Hi,
>
> I would like to know if I can use rampart 1.6.0 al
I have been able to put sp:UsernameToken inside
sp:SignedEncryptedSupportingTokens. I do not know what I did wrong
initially.
Here's what I have now.
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient
"/>
Hi, is it possible to keep a service active but hide it from view under the
/services/listServices path in the axis servlet? We have two services
exposed with different names backed by the same spring managed bean so we
can preserve backwards compatibility with an older client but our newer
service
Hi,
I am using axis2 1.6.0 with rampart 1.6.0 in the client side to invoke a
secured web service which is not a java based.
Please let me know if it is possible to use X509 for WS-Security
authentication based on credentials from keystore, without encryption and
without signature.
If it is, what
Rampart 1.6.0 version have been tested with axis2 1.6.0. BTW it's better
to use 1.6.1 versions.
Thanks !
On Wed, Apr 25, 2012 at 6:41 AM, Natanasabai C wrote:
> Hi,
>
> I would like to know if I can use rampart 1.6.0 along with axis2 1.6.0 in
> the client side to invoke any other secured web
14 matches
Mail list logo
