SOAP Adapter - Change Signature Algorithm

[YouriC]

Hi,

For one of my scenario, I have to change the Signature Algorithm in SOAP Adapter Receiver.

When I try to consume the Web Service, I receive this error :
SECU3518: Invalid digest algorithm 'http://www.w3.org/2000/09/xmldsig#sha1' used. Expecting 'http://www.w3.org/2001/04/xmlenc#sha256'

The problem has been confirmed by the Third Party (WS Provider).

I can not change/adapt the certificate.
He works perfectly with SOAPUI and this settings :

AXIS Adapter is maybe an Alternative but I need to know if it's possible with the SOAP Adapter.

Regards,
Youri

[former_member607993]

Hi Youri,

Please refer the below link which may be help you:

https://blogs.sap.com/2019/05/31/integrating-amazon-simple-storage-service-amazon-s3-and-sap-ecc-v6....

[YouriC]

Hi Rajesh,

Your blog is very interesting.
I will see if I can apply this solution asap.

I also created a SAP Incident for this problem.
I think SAP has to handle SHA256 for Digest Algorithm, it's a W3.org recommendation.

Regards,
Youri

[former_member607993]

Hi Youri,

Yes,please map the User defined function (which generates the Authorization header values dynamically) to XML root node in the Message Mapping.

[former_member607993]

Hi Youri,

You can use UDF in graphic mapper to generate x-amz-content-sha-256 header:

public String generateContentHashing(String payload)

{

StringBuilder payloadSb = new StringBuilder();

try

{

MessageDigest md = MessageDigest.getInstance("SHA-256");

byte[] hashPayloadInBytes = md.digest(payload.getBytes(StandardCharsets.UTF_8));

for (byte b : hashPayloadInBytes)

{

payloadSb.append(String.format("%02x", b));

}

} catch (NoSuchAlgorithmException e) {

e.printStackTrace();

}

return payloadSb.toString();

}

[former_member607993]

Hi Youri,

Did you try this.?

[YouriC]

No, I don't try this approach.

I'm looking for a solution in the Integration Builder with the Communication Channel or Integrated Configuration settings.
Currently I try with the Axis Adapter but I have the same problem :

SECU3518: Invalid digest algorithm 'http://www.w3.org/2000/09/xmldsig#sha1' used. Expecting 'http://www.w3.org/2001/04/xmlenc#sha256'

I found some informations in this note 688983, apparently SAP only uses SHA1 for Digest Algorithm ...

But in the W3.Org documentation : https://www.w3.org/TR/xmlsec-algorithms/#digest-method-uris

SHA-1 is the only digest algorithm defined in [XMLDSIG-CORE] and is mandatory to implement in that specification and in [XMLENC-CORE]. Use of SHA-1 is discouraged in [XMLDSIG-CORE1] and [XMLENC-CORE1] both of which mandate SHA-256 as mandatory to implement and offer a number of other optional SHA algorithms.

[former_member607993]

Hi Youri,

You can try with Java mapping.

[YouriC]

Where to put the UDF ? On my XML root node in the Message Mapping ?