We're deprecating legacy test tokens and will disallow the creation of new test tokens beginning May 5th, 2020.
We launched Slack apps over four years ago as a replacement to the number of ways one could obtain overly-permissive tokens to integrate with Slack.
If you or a software product you author relies on test token creation, you will need to migrate to using Slack apps with specifically named scopes instead.
On May 5th, 2020, you will no longer be able to create new legacy tester tokens.
Existing legacy tester tokens will continue functioning, provided they remain in use.
Third party applications and integrations instructing users to create legacy tester tokens will need to be revised to work with more granular permissions.
Create a Slack app and ask for the permission scopes corresponding to your goals. You can install your app without implementing OAuth by copying and pasting the displayed token to your preferred programming environment.
Tester tokens have more permissions than can be completely described with individual scopes. We don't recommend taking shortcuts by using legacy scopes.
For apps currently using the RTM API with tester tokens, we recommend moving to the Events API. If you must continue using RTM, classic Slack apps can still be created and work with
rtm.connect. This approach involves trading a deprecated approach for a legacy one and is discouraged.
There's nothing you need to do if you don't create or ask people to create tester tokens.
If you use tester tokens to write quick scripts or perform other tasks with the Web API and don't migrate to Slack apps, you won't be able to create new tester tokens after May 5th, 2020.
If you tell users to create tester tokens to use in software you develop, those users will no longer be able to follow your instructions.
We'll stop allowing the creation of new legacy tester tokens beginning May 5th, 2020.
Talk to us about legacy tokens and migrating to Slack apps at email@example.com.Review other recent updates