Encryption Method algorithm for WS security

[Former Member]

Hi there,

We enabled WS security for one of our interface which acts as a consumer to use one web service provided by our partner.

The connectivity is in place and we verified our request was received and processed, but the following is the returned message:

<SAP:AdditionalText>soap fault: Data Encryption Algorithm http://www.w3.org/2001/04/xmlenc#tripledes-cbc not supported. Supported Algorithms are 3DES, AES-128 and AES-256.</SAP:AdditionalText>

We turn on trace in our XI system, and it is true that we used xmlenc#tripledes-cbc as the encryption algorithm. Our partner is saying that they only support AES-128 algorithm.

Now my question is that if we have to change our encryption algorithm to AES-128 in XI? if so, how we can do that?

Thanks in advance..

Jerry Zhang.

[prateek · Accepted solution]

Now my question is that if we have to change our encryption algorithm to AES-128 in XI?

If you have the AES-128 APIs available, then you may create an adapter module to call these API's and encrypt/decrypt the data accordingly. This is a sample case

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek,

Thanks a lot for the information, we are using SOAP adapter in XI 3.0 in this case, also we don't have PGP, we are wondering if there is any place in XI we can control what algorithm it uses for encryption.

Thanks

Jerry.

[bhavesh_kantilal · Accepted solution]

Jerry

Only algorithm's supported by XI as per help .sap are,

The following algorithms are supported:

● 3DES

DES (Data Encryption Standard)

● RC2-40

● RC2-CBC with block encryption 40 bit

● RC2-64

● RC2-CBC with block encryption 64 bit

● RC2-128

● RC2-CBC with block encryption 128 bit

Am not much of a algorithm's expert, but don't think any other option other than the algorithm's displayed in the drop down when doing the configuration of your adapter would be possible as a standard.

Regards

Bhavesh

[Former Member · Accepted solution]

Thanks a lot, Bhavesh.

The problem was solved by asking our partner to add support for 3DES.