On Fri, Mar 11, 2016 at 3:55 PM, Enrique Soriano
wrote:
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.
MG>faux pas
I looked at the version history and the following commit seems to be
related:
http://svn.apache.org/viewvc?rev=1087600=rev
Maybe that's the change between 1.6.4 and 1.7.0 that explains your issue.
Andreas
On Fri, Mar 11, 2016 at 3:55 PM, Enrique Soriano
wrote:
> Hi
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
for my understanding and to be clear
1)you are not implementing rsa-sha256 on Initiator or recipient so the
rsa-sha256 question is a no-op
2)you are not implementing EncryptedKeySHA1 which is for encryption/decryption
only
3)if the web-service is implementing rsa-sha1
Martin Gainty