How To Fix WSS034 - Invalid algorithm (expected &1 &2 &3, received &4)

WSS034 - Overview

• Message type: E = Error

• Message class: WSS - Web Services Security

• Message number: 034

• Message text: Invalid algorithm (expected &1 &2 &3, received &4)

What causes this issue?

The system received an encryption or digest algorithm, which is not
expected according to the system configuration.

System Response

SOAP security processing is aborted.

How to fix this error?

Check the same algorithm suite is configured for consumer and provider.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WSS034 - Invalid algorithm (expected &1 &2 &3, received &4) ?

  SAP Error Message:
  WSS034 Invalid algorithm (expected &1 &2 &3, received &4)
  
  
  Cause:
  This error occurs in SAP's Web Services Security (WS-Security) processing when the cryptographic algorithm used in a received message does not match the expected algorithm(s) configured in the system.
  
  The system expects certain signature or encryption algorithms (e.g., SHA-256, RSA-SHA1, AES256).
  The incoming SOAP message or security token uses a different algorithm than those expected.
  This mismatch can happen due to:
  Configuration differences between the sender and receiver.
  Changes in security policies or certificates.
  Unsupported or deprecated algorithms being used.
  Incorrect or missing algorithm identifiers in the WS-Security headers.
  
  
  
  
  Explanation of the Message Parameters:
  
  &1 &2 &3 — The list of expected algorithms (e.g., http://www.w3.org/2001/04/xmldsig-more#rsa-sha256).
  &4 — The algorithm actually received in the message.
  
  
  
  Solution:
  
  
  Check the Expected Algorithms Configuration:
  
  Review the WS-Security configuration in SAP NetWeaver or the relevant SAP system.
  Go to the Web Service Security settings (e.g., via transaction STRUST, SOAMANAGER, or the Web Service configuration).
  Verify which algorithms are configured as