Configure an X (Formerly Twitter) Authentication Provider

Set Up a Registration Handler

Set Up an X App

Define an X Authentication Provider in Salesforce

1. From Setup, in the Quick Find box, enter Auth. Providers, and then select Auth. Providers | New.
2. For the provider type, select Twitter.
3. Enter a name for the provider.
4. Enter the URL suffix, which is used in the client configuration URLs. For example, if the URL suffix of your provider is MyXProvider, your SSO URL is similar to https://mydomain_url or site_url /services/auth/sso/MyXProvider.
5. For Consumer Key, use the API key from your X app.
6. For Consumer Secret, use the API secret from your X app.
7. To use an Apex registration handler, take these steps.
   1. For Registration Handler Type, select Apex.
   2. For Registration Handler, select an existing Apex class that implements the Auth.RegistrationHandler interface. Or, to create an template for the registration handler, click Automatically create a registration handler template. Edit this class later, and modify the default content before using it.
8. To use a flow for your registration handler, take these steps.
   1. For Registration Handler Type, select Flow.
   2. For Registration Handler, select an existing flow of the Identity User Registration flow type.
   3. Select a default profile. A default profile is required to run the registration handler. If you don't specify a default profile here, set the default profile in the flow itself.

      If you use the Authentication Provider User Registration flow template, the profile that you set here is automatically stored in the defaultProfileId variable.

   4. Select a default account. If you use your authentication provider for Experience Cloud sites, this account stores new internal users.

      If you use the Authentication Provider User Registration flow template, the profile that you set here is automatically stored in the defaultAccountId variable.

9. For Execute Registration As, select an execution user to run the Apex class or flow. The user must have the Manage Users permission.

   Execute Registration As provides the context in which the registration handler runs. In production, you typically create a system user for the Execute Registration As user. This way, operations performed by the handler are easily traced back to the registration process. For example, if a contact is created, the system user creates it.

10. Optionally, set these fields:
    1. If you enter a consumer key and consumer secret, the consumer secret is included in SOAP API responses by default. To hide the secret in SOAP API responses, deselect Include Consumer Secret in SOAP API Responses. Starting in November 2022, the secret is always replaced in Metadata API responses with a placeholder value. On deployment, replace the placeholder with your consumer secret as plain text, or modify the value later through the UI.
    2. For Custom Error URL, enter a URL for the provider to use to report any errors.
    3. For Custom Logout URL, enter a URL to provide a specific destination for users after they log out, if they authenticated using the SSO flow. Use this field to direct users to a branded logout page or destination other than the default Salesforce logout page. The URL must be fully qualified with an http or https prefix, such as https://acme.my.salesforce.com.
       

       Tip Configure single logout (SLO) to automatically log out a user from Salesforce and the identity provider. As the relying party, Salesforce supports OpenID Connect SLO when the user logs out from the identity provider or Salesforce.
    4. To use a portal for X users, select the portal from the Portal dropdown list.
    5. For Icon URL, add a path to an icon to display as a button on the login page for a site. This icon applies to an Experience Cloud site only. It doesn’t appear on your Salesforce login page or My Domain login URL. Users click the button to log in with the associated authentication provider for the site. Specify a path to your own image, or copy the URL for one of our sample icons into the field.
    6. To use the Salesforce multi-factor authentication (MFA) functionality instead of your identity provider’s MFA service, select Use Salesforce MFA for this SSO provider. This setting triggers MFA only for users who have MFA applied to them directly. For more information, see Use Salesforce MFA for SSO.
11. Save your work.

Update Your X App

After you define the X authentication provider in Salesforce, return to your X app. Update your app to use the Salesforce-generated callback URL as the callback URL value in your X app settings.

Note In your X app, make sure that you set up user authentication.

Add the Authentication Provider to Your Login Page