You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed at slackapi/bolt-js#1211, @slack/oauth (and @slack/bolt that relies on it) needs more flexibility to cover real-world use cases such as service account mapping (Slack + other services) and user activity tracking.
My recent pull request #1436 introduces handleInstallPath() as a new easier way to securely handling /slack/install URL requests. With that, now we have the following handlers:
async
method
args
returned value
description
async
handleInstallPath
request, response, InstallURLOptions
void
Build Slack authorize URL, set state to the brwoser, and redirect the installing user to slack.com. This method will be added in v2.5. (by #1436)
Enable developers to have custom logic right after state parameter validation. Before performing oauth.v2.access API call (=installing the app into a workspace), you can do anything here. This will be added in v2.5.
Enable developers to have custom logic right after performing oauth.v2.access API call (=installing the app into a workspace). Before storing the installation result, you can do anything here. This will be added in v2.5.
As discussed at slackapi/bolt-js#1211,
@slack/oauth
(and@slack/bolt
that relies on it) needs more flexibility to cover real-world use cases such as service account mapping (Slack + other services) and user activity tracking.My recent pull request #1436 introduces
handleInstallPath()
as a new easier way to securely handling/slack/install
URL requests. With that, now we have the following handlers:To resolve the issues mentioned at slackapi/bolt-js#1211, we can add more callbacks:
Packages:
Select all that apply:
@slack/web-api
@slack/rtm-api
@slack/webhooks
@slack/oauth
@slack/socket-mode
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: