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
- Create a new app in the X Developer Portal to get your own API credentials.
- In Salesforce, update the Consumer Key and Secret on the existing Auth Provider record.
- Set callback URLs in your X app to match your Salesforce environment (including sandbox).
- Test authentication flows in sandbox before updating production.
- 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
Sign in with LinkedIn to join the conversation
Loading comments...