Discover information on Slack OpenID endpoints If you're using ngrok, use the ngrok public forwarding host as the root. The Redirect URL signifies where Slack should redirect users when they complete the OAuth flow. Navigate to the OAuth & Permissions section and configure a Redirect URL to match your service. Don't fuss too much over either field-no matter what workspace you select, you'll still be able to distribute your app to other workspaces if you choose. App setupįill out your App Name and select the Development Workspace where you'll play around and build your app. Next up, we'll go through the flow in more detail. Again, if you're familiar with legacy Sign in with Slack, you'll use this method instead of users.identity. You use the method to retrieve updated user information.You receive the standard OpenID response sent to your redirect URI, with the expected fields encoded in the id_token.You exchange your access code for an access token using an OpenID method, /, rather than oauth.v2.access.If you've built a legacy Sign in with Slack app and want to know how the new flow relates to the legacy one, these scopes take the place of legacy identity.* scopes. You request the OpenID scopes- openid, email, and profile.You redirect users to a special OpenID endpoint, /openid/connect/authorize, rather than /oauth/v2/authorize.The key differences between Sign in with Slack and a typical OAuth flow for a Slack app are: Here's an overview of the Sign in with Slack process. If you're not familiar with that, you'll want to review the steps of negotiating that OAuth flow. Implementation of the Sign in with Slack follows the flow of our OAuth V2 process. Slack will send users back to your service along with the information you need. You'll create a Slack app, then configure your service so that you redirect users to the right Slack URL. The path to Sign in With Slack is much easier with a package implementation at your disposal. We recommend you make use of one of these packages to take care of the boilerplate surrounding OAuth. OpenID maintains a list of certified implementations of the OpenID Connect standard. The modern Sign in with Slack works with any package that successfully implements the standard. It's based on the OpenID Connect standard, built on top of OAuth 2.0. The Sign in with Slack flow allows users to grant their Slack profile information to your service. Migrate a legacy Sign in with Slack app.Discover information on Slack OpenID endpoints.Check out Sign in with Slack links which allows users to share their Slack profile with you when they click on a link from your service.
0 kommentar(er)
