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

Consider moving away from legacy tokens #69

Open
sabrinabuckets opened this issue Mar 19, 2018 · 2 comments
Open

Consider moving away from legacy tokens #69

sabrinabuckets opened this issue Mar 19, 2018 · 2 comments

Comments

@sabrinabuckets
Copy link

Slack is encouraging developers to build secure Slack apps, and to move away from using the legacy API tokens. As community admins, we have concerns with these requests:

"(user) is requesting a legacy API test token which provides access to your team’s data and their private data. A developer on your team might want this type of token for testing an app or integration, but you should be cautious about who you grant these to. Instead of using legacy tokens, we encourage creating internal integrations which have more controlled access to data.

@sabrinabuckets
Copy link
Author

For clarity - emphasis in comment was provided by the Slackbot notification, and was not added by myself.

@0if
Copy link

0if commented Jul 4, 2020

Bump - legacy tokens have been deprecated, breaking any new set ups

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

No branches or pull requests

2 participants