Loading

Marketing Cloud Engagement Secret Expiration and Time-To-Live (TTL)

Veröffentlichungsdatum: Sep 29, 2026
Beschreibung

Salesforce is introducing expiration dates for all Marketing Cloud Engagement installed package client secrets. Action is required to rotate your existing client secrets before the enforcement deadline to ensure continuous service and protect your environments.

What’s Changing

  • Client Secret Expiration: All newly created client secrets automatically expire 180 days after they are generated.  

  • Existing Client Secret Expiration: Existing secrets begin to expire on September 30, 2026, which is just over 180 days from the original email notification to administrators sent on March 25, 2026.

  • New Secret Format: All secrets generated after March 2026 use a new format that consists of 64-character strings.

  • Admin Visibility: The Installed Package summary page now includes an expiration date column to provide visibility for each installed package.

Why Is Salesforce Making This Change

Salesforce Security identified active threat actor campaigns leveraging customers' publicly exposed Marketing Cloud Engagement API credentials (client secrets) to gain unauthorized access, send phishing emails, and exfiltrate data. This global security update protects customer environments and the broader Marketing Cloud ecosystem. It isn't the result of an incident affecting any specific instance.

When Does This Change Take Effect

March 25, 2026: Introduced proactive security measures, including the 180-day TTL policy, new secret format, and summary page updates.

September 30, 2026: Initial date for existing client secrets for installed packages to be rotated before they automatically expire. Secret expirations are staggered based on standard release cohorts. Select customers with high API call volumes will be included in R3. 

 

Cohort

MCE Stacks

Enforcement Date

R0 minus select high API volume customers

S8

Sep 30, 2026

R1 minus select high API volume customers

S4, S50 , S401, S406

Oct 1, 2026

R2 minus select high API volume customers

S11, S12, S13, S402, S403

Oct 5, 2026

R3 plus select high API volume customers

S1, S5, S6, S7, S10, S51

Oct 6, 2026

Who’s Affected

These changes affect all customers with installed packages that contain the API Integration component with Server-to-Server or WebApp types. The secret expirations that begin on September 30, 2026 affect all installed packages that use credentials that haven't been rotated since March 25, 2026.

What to Expect

Existing client secrets for installed packages have been assigned an expiration date of September 30 to October 5, 2026, based on the 180-day expiration policy and the staggered enforcement schedule. Admins can view the expiration date for each client secret on the Installed Package summary page. If client secrets are not rotated before their expiration dates, they expire automatically. This expiration will cause service disruptions for integrations that use those client secrets.

Lösung

Before Deadline: How to Prepare

  • Follow Rotation Instructions: For each installed package, generate a staged client secret. For more information, see Rotate an OAuth 2.0 Secret.

  • Update Applications: Update all applications or integrations to use the newly generated client secret. For more information about identifying API integrations that need to be updated, see Audit Content Builder Assets (CloudPages & Emails) for Hardcoded Secrets with SSJS.

  • Activate the Secret: After you update your apps and integrations, activate your newly generated client secrets. New secrets only function after they've been activated.

Ongoing Monitoring

  • Admin Verification: Use the Expiration Date column on the Installed Package summary page to monitor and track the status of client secrets.

  • Routine Rotations: Proactively rotate client secrets at least every 6 months. To prevent service disruptions, rotate secrets before they expire.

Common Questions

Q: How should API clients handle secret expirations?
A: API clients use the client ID and client secret to authenticate and obtain access tokens for API calls. When a client secret expires, the authentication request fails with HTTP 401 Unauthorized (invalid_client). Authentication failures should be monitored on the client side, so that an administrator can rotate expired secrets through the Marketing Cloud Engagement user interface and update the client configuration. Clients should not continuously retry an authentication request after receiving a 401 Unauthorized response.As a best practice, administrators should proactively clean up unused API integrations with expired secrets by deleting the entire installed package. Note that individual API integration components cannot be deleted independently.

Q: How can I further enhance the security of my MCE environment?
A: In addition to rotating client secrets, Salesforce strongly recommends auditing public repositories (such as GitHub, GitLab, Postman collections, and documentation) for exposed credentials. You should also implement IP Allowlisting for all API integration accounts, and enable Audit Trail to monitor MCE login history for anomalous activity, unexpected locations, or unknown IP addresses.

Change Log

Date

Change

September 29, 2026
  • Added the staggered release dates for Sep-Oct, 2026 secret expiration and rotation in the "When Does This Change Take Effect" section

  • Added a FAQ on handling secret rotations

July 20, 2026Initial publication

 

Nummer des Knowledge-Artikels

005389124

 
Laden
Salesforce Help | Article