How To Fix CLB660 - No SHA1 signature provided from SSFA

SAP Error Message - Details

• Message type: E = Error

• Message class: CLB - SAIL: Common messages

• Message number: 660

• Message text: No SHA1 signature provided from SSFA

What causes this issue?

A call to the service provider required an authentication using the
RSA-SHA1 algorithm. For this a signature has to be retrieved from the
SSFA. This signature has not been returned from SSFA.

System Response

The method execution is cancelled.

How to fix this error?

Check the configuration with transactions <DS:TRAN.SSFA>SSFA</> and
<DS:TRAN.STRUST>STRUST</>.

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 CLB660 - No SHA1 signature provided from SSFA ?

  The SAP error message CLB660 No SHA1 signature provided from SSFA typically occurs in the context of SAP's Secure Store and Forward Architecture (SSFA) when there is an issue with the digital signature of a message or document being processed. This error indicates that the system expected a SHA1 signature but did not receive one.
  Cause:
  
  Missing Signature: The most common cause is that the message or document being processed does not have a SHA1 signature attached to it.
  Configuration Issues: There may be misconfigurations in the SSFA settings or in the way the signatures are generated or validated.
  Data Corruption: The data being sent may have been corrupted or altered, leading to the absence of the expected signature.
  Version Mismatch: There could be a mismatch between the versions of the components involved in the signature generation and validation process.
  
  Solution:
  
  Check Message Generation: Ensure that the message or document being sent includes a valid SHA1 signature. This may involve reviewing the code or process that generates the message.
  Configuration Review: Review the SSFA configuration settings in your SAP system to ensure that they are correctly set up to handle signatures.
  Update Components: If there is a version mismatch, consider updating the relevant components of your SAP system to ensure compatibility.
  Error Handling: Implement error handling in your application to catch and log instances where a SHA1 signature is missing, allowing for easier troubleshooting in the future.
  Consult Documentation: Refer to SAP documentation or support notes related to SSFA and digital signatures for any specific guidance or updates that may address this issue.
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to the CLB660 error message. SAP frequently releases notes that provide fixes or workarounds for known issues.
  SSFA Documentation: Review the official SAP documentation on Secure Store and Forward Architecture for best practices and configuration guidelines.
  Community Forums: Engage with SAP community forums or support channels where other users may have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.