For security reasons, Salesforce Certificates expire within 12 months of your purchase and require you to follow the steps below to renew.
The customer will receive an email in their inbox reminding you to renew your MuleSoft Composer certificate 10 months after purchase, and 60 and 30 days before the certificate expires.
The reminder email will be titled, 'SFDC Expiring Certificate Notification.' An example email is shown below, where the MuleSoft Composer certificate is designated.
When the MuleSoft Composer certificate is about to expire, please select one of the following options:
Option 1:
1) In Salesforce, go to Setup → Process Automation → MuleSoft Composer
2) Configure MuleSoft Services → press the Initiate Configuration button
3) Performing this action will generate a new Salesforce Certificate
1) In Salesforce, go to Setup → Security → Certificate and Key Management
2) You can see that the existing certificate - "mulesoft_composer_certificate" might be expiring soon.
Note: Self-signed certificates with key size 2048 are valid for 1 year only.
Since these are self-signed certificates, we can delete them and re-create to extend the active period. But before we can delete, ensure that a new certificate is created and replaced in the referred Named Credential.
3) Create a new self-signed certificate with any name and key size as 2048.
4) Update the name credential with the newly created certificate.
5) Delete the old certificate that is about to expire.
6) Since the MuleSoft Composer Package will look for the exact match, update the name of the newly created certificate to - "mulesoft_composer_certificate". (This cannot be done in the beginning as the system will not allow duplicate names). The name change will automatically reflect in the named credential.
NOTE: The permission required to perform "Initiate Configuration" to renew an expired certificate is Salesforce Admin with System Administrator profile. For more info, please check the doc here.
Note:
During certificate renewal, please ensure that Option 2 is completed first. Once this step is finished, the “Initiate Configuration” button will become available. It is required to click this button to reset the configuration—otherwise, the setup may result in errors.
Please note that the current steps in this article primarily reflect the initial setup flow. For certificate renewals, the above sequence must be followed.
If after following these steps you still experience issues, please open a new Salesforce Support case for the MuleSoft Composer product.
000390883

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.