Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changes to bot & user scopes #194

Open
javamonkey79 opened this issue Apr 8, 2020 · 1 comment · May be fixed by #211
Open

changes to bot & user scopes #194

javamonkey79 opened this issue Apr 8, 2020 · 1 comment · May be fixed by #211

Comments

@javamonkey79
Copy link

With the current version of the API, the scopes only allow User Token Scopes to read channel history, but only allow Bot Token Scopes to post messages.

As far as I can tell, the only workaround is to now set both the user and bot tokens of the app.

@christofdamian
Copy link

I hacked this locally in the script. It should be fairly easy to pass this through from the configuration.

christofdamian added a commit to christofdamian/destalinator that referenced this issue Apr 14, 2021
Allow passing both the bot and user token to the scripts via the environment
variables DESTALINATOR_API_BOT_TOKEN and DESTALINATOR_API_USER_TOKEN. They have
different permissions and the bot token is only used to post messags, all other
calls use the user token. Fixes randsleadershipslack#194.

This also includes randsleadershipslack#210 and fixes randsleadershipslack#209 by moving the tokens into the header
instead of using query parameters.

Don't pass `as_user` to Slack, as this has been removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants