How To Fix SAML2120 - Can not get certificate's public key

SAP Error Message - Details

• Message type: E = Error

• Message class: SAML2 - SAML2 Nachrichten

• Message number: 120

• Message text: Can not get certificate's public key

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SAML2120 - Can not get certificate's public key ?

  The SAP error message SAML2120: Can not get certificate's public key typically occurs in the context of Single Sign-On (SSO) configurations using SAML (Security Assertion Markup Language). This error indicates that the system is unable to retrieve the public key from the specified certificate, which is essential for validating SAML assertions.
  Causes:
  
  Invalid Certificate: The certificate may be corrupted, expired, or not properly formatted.
  Missing Certificate: The certificate might not be present in the expected location or not imported correctly into the SAP system.
  Incorrect Configuration: The configuration settings for the SAML identity provider (IdP) or service provider (SP) may be incorrect, leading to issues in accessing the certificate.
  Access Issues: There may be permission issues preventing the SAP system from accessing the certificate file.
  Key Store Issues: If the certificate is stored in a key store, there may be issues with the key store configuration or access.
  
  Solutions:
  
  
  Check Certificate Validity:
  
  Ensure that the certificate is valid and not expired. You can check the certificate details using tools like OpenSSL or keytool.
  
  
  
  Re-import the Certificate:
  
  If the certificate is missing or corrupted, re-import the correct certificate into the SAP system. This can typically be done using transaction codes like STRUST or STRUSTSSO2.
  
  
  
  Verify Configuration:
  
  Review the SAML configuration settings in the SAP system. Ensure that the certificate is correctly referenced in the SAML configuration.
  Check the settings for the IdP and SP to ensure they match and are correctly configured.
  
  
  
  Check Key Store Configuration:
  
  If using a key store, verify that the key store is correctly configured and accessible by the SAP system. Ensure that the necessary permissions are set.
  
  
  
  Review Logs:
  
  Check the SAP system logs (transaction SLG1) for more detailed error messages that may provide additional context for the issue.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or guides related to SAML configuration and certificate management for specific instructions and best practices.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAML Configuration: Familiarize yourself with the SAML configuration process in SAP, including how to manage certificates and trust relationships.
  Security Best Practices: Ensure that you follow security best practices when managing certificates, including regular updates and audits.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.