Skip to main content

We have one internal certificate which is expiring on 17th. our functionality is working fine with the certificatte going to expire on 17th but getting error with new CA signed certificate . 

 

We are receiving the ERROR: System.CalloutException: Received fatal alert: unsupported_certificate. 

 

How to resolve this and what could be the issue. 

3 Antworten
  1. 15. Dez. 2025, 11:39

    Hi @Alok Jha

    The System.CalloutException: Received fatal alert: unsupported_certificate error occurs during the SSL/TLS handshake when Salesforce (the client in the callout) tries to establish a secure connection with your external endpoint and the new certificate is rejected by Salesforce's trust store.

    The issue is likely that the Certificate Authority (CA) that signed your new certificate is not trusted by Salesforce, or the certificate chain is incomplete.

    What Could Be the Issue

    The core problem is one of trust and compatibility:

    1. Untrusted CA Root: The Root Certificate Authority (CA) that signed your new certificate is not present in the list of CAs that Salesforce trusts by default. Salesforce maintains a specific list of trusted root CAs.
    2. Incomplete Certificate Chain: The external server might not be sending the full certificate chain (including all necessary intermediate certificates) during the handshake process. The older certificate might have had a simpler chain that was already cached or included, while the new one requires intermediaries that are not being provided by the server.
    3. Unsupported Certificate Purpose/Key Usage: The new certificate might have key usage extensions that are incompatible with the SSL client purpose required by Salesforce callouts (e.g., missing "clientAuth" key usage).

    How to Resolve This

    You need to verify the certificate chain and ensure compatibility with Salesforce's trust requirements.

    1. Verify the Certificate Chain Installation on the External Server

    The most likely fix is ensuring the full chain is installed on the server hosting the endpoint.

    • Action: Ask the administrator of the external endpoint to check if they have installed all intermediate certificates provided by the CA on their server. An incomplete chain will cause Salesforce to reject the connection.

    2. Verify the CA is Trusted by Salesforce

    Check if the Root CA used for the new certificate is in Salesforce's trust store.

    • Action: In your Salesforce org, you can check the list of trusted CAs by going to the URL: https://<Your MyDomain> (replace <Your MyDomain> with your org's My Domain name).
    • Result: If your new certificate's root CA is not in this list, you must acquire a certificate from a trusted CA.

    3. Use OpenSSL to Diagnose the Certificate

    You can use the openssl command-line tool to inspect the certificate chain the server is presenting.

    • Command: 

      bash

    openssl s_client -connect <hostname>:<port>

     

    • Analysis:
      • This command will display the certificate chain sent by the server. Verify that the chain is complete and links back to a trusted root CA in the Salesforce list.
      • You can also check the certificate purpose using: openssl x509 -in leaf.pem -noout -purpose to ensure it includes SSL client purposes if using two-way SSL.

    By following these steps, you should be able to identify whether the issue is with the CA signer itself or an incomplete installation of the certificate chain on the external server.