r 12, 2016 at 2:16 AM, Martin Gainty wrote:
>
>
> On Fri, Mar 11, 2016 at 3:55 PM, Enrique Soriano <
> enrique.sori...@gmail.com> wrote:
>
> Hi Martin, I really appreciate your efforts to help me, but I think you
> didn’t understand the problem.
>
> The client
Hi Martin, I really appreciate your efforts to help me, but I think you
didn’t understand the problem.
The client stubs generated by Axis2 1.7.1 were sending rsa-sha256
signatures, this is a fact.
The server I need to use requires rsa-sha1 signatures, this is a fact.
The client stubs generated b
Hi Martin, thanks for your response (again).
I've solved the problem by downgrading to axis2-1.6.4. Now the client
stubs generated by wsdl2java work ok.
Maybe it's just a bug in Axis2 2-1.7.1 (??).
>> how would client signing with rsa-sha1 algorithm be able to communicate with
>> any webservice
On Mar 9, 2016 15:34, "Martin Gainty" wrote:
>
> 2000 spec you are
> currently implementing:
>
>
> does not acommodate
>256 bit signatures
>
> your current option will only
>allow 2000 xmldsig spec which is why
>you are defaulting to rsa-sha1
>algorithm in SignatureMethod
I want to use rsa-sha1,
First of all, thanks for the prompt response.
>>>which specific algorithm do you want to implement on the server?
I'm trying to implement a client for an existing server. The server
only accepts rsa-sha1 signatures.
I can't read or modify the server code, I only have the WSDL to
generate the clie
Hi all, I need some help with Axis2/rampart.
I'm implementing a WS client. I generated the client stubs from a WSDL
file by using wsdl2java (jaxbri binding). The WSDL file includes a
WS-security policy, which sets TripleDesSha256Rsa15 as the
AlgorithmSuite.
Rampart is engaged, my Keystore is ok,
