SAP Knowledge Base Article - Preview

2975420 - SsfVerify failed: rc=5, SSF_API_SIGNER_ERRORS, "signer r c=27", SSF_API_SIGNER_NOT_OK

Symptom

  • Error "SsfVerify failed: rc=5, SSF_API_SIGNER_ERRORS, "signer r c=27", SSF_API_SIGNER_NOT_OK" occurs.
  • This error is issued by actions related to the SAP Content Server, therefore it can be thrown in many different application transactions. 
  • This error may also be seen in the output when running the content repository test reports RSCMST*.
  • In some cases, the <repository>.pse and <repository>.certs files are copied from old Content Server to the SECUDIR of the Content Server 7.5* after upgrade from a lower version of SAP Content Server to 7.5*.


Read more...

Environment

  • SAP Content Server 7.53 upwards
  • SAP Basis release independent

Keywords

SsfVerify failed, rc=5, SSF_API_SIGNER_ERRORS, signer r c=27, SSF_API_SIGNER_NOT_OK, CSADMIN, Document Location, crepid.certs, crepid.pse, .certs, .pse, invalid password, signer, 401, authorization required, SsfVerify, 7.53, SP726, SSF_API_DECODE_FAILED, KPRO, content, repository, server , KBA , BC-SRV-KPR-CS , SAP Content Server , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.