...
Snaps in the Salesforce Snap Pack that use the Salesforce Mutual Authentication account must configure the setup in the Salesforce portal to function without any issue. For enabling
To enable mutual authentication in Salesforce, follow the these steps below.:
Log on to into the Salesforce portal.
Navigate to Go to Setup > Security Controls > Certificate and Key Management. The following page is displayed.
By default, you cannot view the Mutual Authentication Certificate section. In such case, you need to raise a request to the Salesforce Support team to enable this section.
Once this section is enabled, you need a CA signed certificate to upload in this section. See “Create CA signed certificate” for more information.
Once you are ready with a have the CA signed certificate, click Upload Mutual Authentication Certificate.
Provide a label and name for your certificate.
Click Choose File to locate the certificate.
Click Save to save the upload.
Create a custom profile to enable the “Enforce SSL/TLS Mutual Authentication” user permission for an
API Onlyuser.
...
To create a CA Signed Certificate:
Log on to into the Salesforce portal.
Navigate to Setup.
Enter Certificate and Key Management in the Quick Find box, and then select Certificate and Key Management.
Select Create CA-Signed Certificate.
Enter a descriptive label for the Salesforce certificate. This name is used primarily by administrators when viewing certificates.
Enter a unique name. You can accept the name that’s populated based on the certificate label you enter.
Note: Use a unique name when referring to the certificate using the Lightning Platform web services API or Apex.This The name can contain only underscores and alphanumeric characters, and must be a unique name in your org.
It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
Select a key size for your certificate and keys.
For securing data in transit through TLS, we recommend you to use the default 2048-bit key size.Enter the following information. These fields are combined to generate a unique certificate.
Common Name: The fully qualified domain name of the company requesting the signed certificate, generally of the form http://www.mycompany.com .
Email Address: The email address associated with this certificate.
Company: The legal name of your company or your legal name.
Department: The branch of your company using the certificate, such as marketing or accounting.
City: The city where the company resides.
State: The state where the company resides.
Country Code: A two-letter code indicating the country where the company resides. For example, the value for United States is US.
Click Save to save the Salesforce certificate.
The certificate and corresponding keys are automatically generated.Find your new certificate from the certificates list, then click Download Certificate Signing Request.
Note: Downloaded certificate signing requests have .CSR extensions.Send the certificate request to the certificate authority of your choice. For example, GoDaddy.
After the certificate authority returns the signed certificate, go back to Certificate and Key Management, click the name of the certificate, then click Upload Signed Certificate.
The CA-signed certificate must match the certificate created in Salesforce. If you upload a different CA-signed certificate, the upload fails.Click Save to complete the upload process.
...
| Note |
|---|
Once you run the |
...
the certificate chain is incomplete. To check the intermediate certificate, first inspect the issuer of the certificate shared by CA using the following command: Note down the Issuer: CN name. The CN is the Intermediate Certificate. |
...
Go to the Issuer: OU site mentioned in the above output to get the required intermediate certificate. |
...
For example, https://certs.godaddy.com/repository |
...
Download the intermediate certificate pem file.
...
| Info |
|---|
You can verify the accuracy of the chosen intermediate certificate |
...
using the following command:
|
| Cfm round rect |
|---|
...
You can attach the pem file with |
...
the certificate pem using the below command.
|
| Cfm round rect |
|---|
NOTE : The certificate chain order should look like belowmust meet the following requirements:
|
...
|
...
So for testing through Snap , we need a KeyStore file which should have an intermediate certificate as well. Follow the section Creating JKS from pem.
See Also