Release Update: Salesforce-Managed X (Twitter) Auth Provider Retiring

Salesforce is retiring the centrally-managed X authentication provider. After enforcement, any org still relying on it for SSO or API integrations will lose that authentication capability entirely.

Where

Setup > Auth Providers — check for any provider with Type = Twitter.

How

  1. Create a new app in the X Developer Portal to get your own API credentials.
  2. In Salesforce, update the Consumer Key and Secret on the existing Auth Provider record.
  3. Set callback URLs in your X app to match your Salesforce environment (including sandbox).
  4. Test authentication flows in sandbox before updating production.
  5. Schedule production changes during low-traffic periods.

Why

Salesforce is no longer maintaining shared API keys for X. Each org needs its own X Developer account and credentials going forward. Act before enforcement to avoid login or integration outages.

💬 Comments

Loading comments...