Loading
Salesforce now sends email only from verified domains. Read More
Identify Your Users and Manage Access
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Configure a Slack Authentication Provider

            You are here:

            1. Salesforce Help
            2. Docs
            3. Identify Your Users and Manage Access

            Configure a Slack Authentication Provider

            Configure a Slack authentication provider so your users can log in to Salesforce using their Slack credentials.

            Required Editions

            Available in: Lightning Experience and Salesforce Classic
            Available in: Enterprise, Performance, Unlimited, and Developer Editions
            User Permissions Needed
            To view the settings: View Setup and Configuration
            To edit the settings:

            Customize Application

            AND

            Manage Auth. Providers

            To configure Slack as an authentication provider, follow these steps.

            1. Set up a registration handler.
            2. Set up a Slack app.
            3. Define a Slack authentication provider in Salesforce.
            4. Update your Slack app to use the Callback URL generated by Salesforce as the redirect URL in Slack.
            5. Test the single sign-on (SSO) connection.
            6. Add the Slack authentication provider to your login page.
            Note
            Note For sandbox use cases, you can skip some of these steps and use the Salesforce-managed Slack app. For production use cases, always create your own Slack app and use its credentials for your authentication provider. The Salesforce-managed app can experience downtime and isn't recommended for production.

            Set Up a Registration Handler

            To use an authentication provider for single sign-on, you must create a registration handler. The registration handler creates users and updates existing users who access Salesforce via the identity provider. You can set up a registration handler with Apex or Flow Builder. For more information, see Create an Authentication Provider Registration Handler.

            Set Up a Slack App

            Before you can configure Slack for Salesforce, set up an app in Slack.

            Note
            Note You can skip this step by allowing Salesforce to use its own default app. For more information, see Use Salesforce Managed Authentication Providers.
            1. Go to the Slack developer website and create an app.
            2. Modify the app settings as needed.
            3. Note the App ID and Client Secret.

            Define a Slack Provider in Salesforce

            To set up a Slack provider in Salesforce, you need the Slack App ID and Client Secret.

            1. From Setup, in the Quick Find box, enter Auth, and then select Auth. Providers.
            2. Click New.
            3. For the provider type, select Slack.
            4. Enter a name for the provider.
            5. Enter the URL suffix, which is used in client configuration URLs. For example, if the URL suffix of your provider is MySlackProvider, your SSO URL is similar to https://mydomain_url or site_url/services/auth/sso/MySlackProvider.
            6. For Consumer Key, use the Slack App ID.
            7. For Consumer Secret, use the Slack Client Secret.
            8. Optionally, set these fields.
              • For Authorize Endpoint URL, enter the base URL from Slack. For example, https://slack.com/openid/connect/authorize. If you leave this field blank, Salesforce uses the version of the Slack API that your app uses.
              • For Token Endpoint URL, enter the URL from Slack. For example, https://slack.com/api/openid.connect.token. If you leave this field blank, Salesforce uses the version of the Slack API that your app uses.
              • To change the values requested from Slack’s profile API, enter the User Info Endpoint URL. For example, https://slack.com/api/openid.connect.userInfo. The requested fields must correspond to the requested scopes. If you leave this field blank, Salesforce uses the version of the Slack API that your app uses.
              • For Default Scopes, enter the scopes to send along with the request to the authorization endpoint. Otherwise, the hard-coded defaults for the provider type are used.
              • 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.
              • For Custom Error URL, enter the URL for the provider to use to report errors.
              • 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.
            9. 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.
            10. 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.

            11. 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.

            12. 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.
            13. Save your provider.
            14. Note the generated Auth. Provider ID value. You use it with the Auth.AuthToken Apex class.

            Several client configuration URLs are generated after defining the authentication provider.

            • Test-Only Initialization URL—Salesforce admins use this URL to ensure that the third-party provider is set up correctly. The admin opens this URL in a browser, signs in to the third party, and is redirected to Salesforce with a map of attributes.
            • Single Sign-On Initialization URL—Use this URL to perform SSO into Salesforce from a third party using its third-party credentials. The user opens this URL in a browser and logs in to the third party. The third party creates a user or updates an existing user. Then the third party signs the user into Salesforce as that user.
            • Existing User Linking URL—Use this URL to link existing Salesforce users to a third-party account. The user opens this URL in a browser, signs in to the third party, signs in to Salesforce, and approves the link.
            • OAuth-Only Initialization URL—Use this URL to obtain OAuth access tokens for a third party. Users must authenticate with Salesforce for the third-party service to get a token. This flow doesn’t provide for future SSO functionality.
            • Callback URL—Use this URL for the endpoint that the authentication provider calls back to for configuration. The authentication provider must redirect to the callback URL with information for each client configuration URL.
            • Single Logout URL—Use this URL to log users out from multiple apps with a single logout. For example, the user logs out of Salesforce and is automatically logged out of the third-party provider.

            Client configuration URLs support additional request parameters that enable you to direct users to log in to specific sites, obtain customized permissions from the third party, or go to a specific location after authenticating.

            Update Your Slack App

            After defining the authentication provider in Salesforce, go back to Slack and update your app to use the callback URL from Salesforce as the redirect URL in Slack.

            Add the Authentication Provider to Your Login Page

            Configure your login page to show the authentication provider as a login option. Depending on whether you’re configuring SSO for an org or Experience Cloud site, this step is different.

             
            Loading
            Salesforce Help | Article