Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3280

SOAP(axis) receiver scenario - signature verification is invalid

$
0
0

Hi,

The problem in a nutshell is that axis modifies the response message(add "blank lines, spaces, tabs") and signature validation fails, detailed explanation:

 

There is a webservice that uses WS-Security token profile x509 1.0, both the request and the response, and SAP PI should consume this webservice.

I set the whole scenario, and when testing, I see that the request is properly signed, but validation of the response message signed failure.

 

I use the tcpgateway to see what was the response message and compare it with the message that I see in the log of the NWA, I see that was modified by axis, some images:

 

Original response message from tcpgateway:

Captura de pantalla 2015-09-20 a la(s) 16.53.10.png

Modified message from NWA:

 

Captura de pantalla 2015-09-20 a la(s) 16.53.28.png

 

And the result of signature verification:

Captura de pantalla 2015-09-20 a la(s) 16.53.57.png

 

I have found in note "1039369 - FAQ Axis XI Adapter" question "11.I am getting a corrupted signature" of the section "Advanced usage questions" a similar problem but the sender scenario, which it proposes using the parameters "enableNamespacePrefixOptimization -> false" and "disablePrettyXML -> true" to solve the problem, but for the scenario receiver does not, some images:

 

Configuration:

sdn.png

Message modified from NWA(you can see that there is less blank lines, but not the original message !!!):

sdn2.png

And the result of signature verification(this difference between the calculated and digest sent!):

sd3.png

At first I thought the problem was WSS4J but I used all versions (1.5.4, 1.5.5, 1.5.6, 1.5.7) and the problem was always the same, but seeing the log NWA not me doubts remain.

 

any ideas?.

 

Best regards.


Viewing all articles
Browse latest Browse all 3280

Trending Articles