Salesforce-Managed X (Formerly Twitter) Authentication Provider Retirement (Release Update)
The Salesforce-managed app for the X (formerly Twitter) authentication provider is being retired. This update breaks any single sign-on (SSO) configurations that use the Salesforce-managed X app. To avoid disruptions, create a custom X app and update your SSO configurations.
Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
When: Salesforce enforces this update in Summer ’26. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab.
Why: Some X authentication providers use an X app that Salesforce manages. With the Salesforce-managed X app, you can leave the consumer key and secret blank when you set up the authentication provider. In Spring ’24, Salesforce removed the ability to use the Salesforce-managed X app for new authentication providers, but continued to support it for existing authentication providers that were created before Spring ’24.
Now, the Salesforce-managed X app is being fully retired. Instead, you must use a custom X app and specify its consumer key and secret in your authentication provider configuration. With a custom X app, you have more control over your SSO configuration.
How: If an X authentication provider uses the Salesforce-managed app, it stops working when this release update is enforced. Users can no longer use the authentication provider to log in via SSO.
To review this update, from Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. For Salesforce-Managed X (Formerly Twitter) Authentication Provider Retirement, follow the testing and activation steps.