Configure Sign in with Slack links using Auth0

Sign in with Slack (SIWS) links allow a user to share their Slack identity with your app when they click on a link from your service. When a user clicks on your link, Slack will utilize OpenID Connect (OIDC) standard to send over a user’s identity information.

Before continuing with this guide, you might want to read the following before proceeding:

  1. Sign in with Slack documentation
  2. OpenID Connect 1.0 specification (can be skimmed or used as reference)

Sign in with Slack links is a paid feature. Interested parties should fill out the interest form or reach out to for more information.

Let's jump in!

Prerequisites to use this feature:

  1. Your Slack app is using granular permissions
  2. You are able to implement Sign in with Slack using OpenID Connect
  3. You are able to implement automatic provisioning and account linking within your product

Domain Verification

In order to receive a user’s information when a link is clicked, you will first need to verify that you own your domain(s). This domain must be different from your production domain.

Please reach out to to request Domain Verification be enabled for your team.

To verify a domain, locate your app from your Apps page then navigate to your app's "Domain Verification" page. The Domain Verification link is under the "Settings" section in the top of the left sidebar.

This should take you to:<team_id>/<app_id>/domain-verification where you can add and verify domains for Sign in with Slack links.

Once you've added and verified your domains you will need to reach out to Slack to confirm your domains.

Implement Sign in with Slack

You will need to implement Sign in with Slack for your service using OpenID Connect.

Setting up Open ID

  1. Choose an existing OpenID Connect Relying Party client for your tech stack (or create your own by following the standard) and point it towards Slack’s provided OpenID configuration URL. For this guide, we are using Auth0 as our client, but feel free to use whichever you’d like.

  2. Navigate to your App Configuration Oauth and Permissions page and add a redirect URL where you would like the OpenID flow to redirect after it’s completed and click save.

For an Auth0 service, this may look like:

  1. Add the following User Token scopes to enable Sign in with Slack. You'll need the following scopes:

Keep track of your Client ID and Client Secret from the Basic Information Page.

  1. Navigate to your OpenID connect Relying Party client (Auth 0) for us, and navigate to Enterprise and then Connections. Next, click on, OpenID Connect to create a new connection.
  • For Logo URL, feel free to use this sample URL:

  • For Issuer URL, please use this URL (the key param will be required until we publicly release this feature):

We support both Front Channel and Back Channel types.

  1. If you use Back Channel, enter your Client Secret as well. Click Issuer Details and check whether or not the Token Endpoint is filled in. If it is not filled in, please enter:

(This endpoint is subject to change - we will alert you if we change it)

  1. Under Scopes, leave openid profile email but add the identity scopes from your Slack App scopes. It should look like this:

openid profile email identity.basic identity.avatar

  1. Click Save Changes.

For reference, here is a fully filled out Auth0 Configuration page:

From the OpenID Connect page, click the Try button and this should now work!

We have noticed that using the Front Channel method means that cookies are not sent by default in Chrome once the form_post actually posts due to the SameSite restriction. If this means nothing to you, feel free to ignore!

Implement automatic account provisioning and/or linking

After the domain has been configured, verified and enabled, when a link (e.g. that conforms to the domain pattern is first clicked in Slack, Slack will prompt the user if they would like to additionally transfer their Slack identity to you. If users do not accept and decline 3 times, subsequent links clicked will not trigger this prompt.

SIWS Modal

If a user clicks Accept, Slack will redirect the user to an endpoint with a login hint to start the identity transfer.

If the user clicks Decline, we will simply redirect to the link clicked.

Slack will redirect to a login initiation endpoint that you have specified in your App Configuration Pages with the following parameters:

name value notes
login_hint JWT-encoded target user information Option to JWT decode this and check if the target user is already logged-in, bypassing the OpenID connect flow

The OpenID Connect specification for Initiating Login from a Third Party specifies how this endpoint is used:

After receiving the request, your app will start an OpenID Connect authentication similar to the Sign in with Slack flow described above but appending the login_hint parameter to the authorization URL.

When the flow is complete, there should be an additional key set with the claims called:

which is the URI that the user originally clicked. Note that Auth0 renames this key to:


SIWS links Sample Workflow

What does SIWS links look like when it’s all setup in your app?

  1. Your app will send an Authentication Request to a Slack endpoint (e.g.
      GET /siws/authorize?
        &nonce=n-0S6_WzA2Mj HTTP/1.1
  1. Slack will verify the request but will not conduct End-User Consent authorization, it will proceed without prompting the user. If the login_hint does not match an existing stored link click, the Authentication Request will fail.
  2. Slack will send a Authentication Response to your app by sending a POST to your response endpoint (e.g. with the following parameters:
name value
id_token JWT-encoded payload
expires_in 300
state matches state sent in Authentication Request
  1. After decoding, the JWT-encoded payload will include the following:

        "iss": "",
        "sub": "",
        "aud": "6371490080.1055357699042",
        "exp": 1592939535,
        "iat": 1592939235,
        "auth_time": 1592939235,
        "nonce": "n-0S6_WzA2Mj",
        "email": "",
        "locale": "en-US",
        "name": "John Smith",
        "given_name": "John",
        "family_name": "Smith",
        "picture": "",
        "": "U06AXEE2U",
        "": "",
        "": "",
        "": "",
        "": "",
        "": "",
        "": "",
        "": "",
        "": "T06AXEE2C",
        "": "John Testy",
        "": "johntesty",
        "": "",
        "": "",
        "": "",
        "": true,
        "": ""
  2. You MUST verify that the nonce matches the one originally sent. It should also verify the JWT using the JWKS defined by Slack and verify that the JWT has not expired.

  3. You can now check if an account with this email already exists. If it does not, you can automatically provision an account for this user. If it does, it will add Sign in with Slack as an additional login method for this account.

Next steps

Was this page helpful?