-
Notifications
You must be signed in to change notification settings - Fork 885
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
when deploy to heroku, get error: Legacy tester tokens may no longer be created. #143
Comments
facing the same problem can no longer create a legacy token |
even for the exist slack channel which I had token actived, Slack starts taking them back. ============================== May 20, 2020, 1:23:51 PM PDT Hi there, We've noticed that an API tester token associated with your account on xxx.slack.com has not been used in a while. You may have generated this token to simply test our API methods or used it in an app to access your workspace and automate a workflow. API tester tokens are quite powerful and it is a best practice to revoke them if they are not being used. We have gone ahead and revoked your tester token since it has been inactive for quite some time. If your token was used with an app or integration (such as a bot), then these integrations will no longer work. We hope there won’t be a disruption, but believe that maintaining the security of your workspace and privacy of your communications is important enough to take this action. Here are the details of the tester token we've revoked. This action cannot be reversed. Please see the suggestions outlined below about how to generate new tokens by creating a new Slack app: Token xoxp-xxx-... There is no further action needed from your side if you are not intending to continue to use this specific token. That said, if your workspace relies on API tester tokens for bots, integrations, or using the SCIM API, please read https://slack.com/help/articles/215770388 for information on how to issue new authentication tokens. Please note, however, that we are in the process of phasing out API tester tokens and moving towards a "bring your own token" model for testing our API. This means that you should create a Slack app with the appropriate scopes for the API methods you wish to use. We have updated our API method tester pages so that you can use your own token when submitting a test API request. Previously you were only able to select a generated tester token from the token argument dropdown. You can create a new Slack app at https://api.slack.com/apps/new. Required scopes for the various API methods are listed at https://api.slack.com/docs/oauth-scopes#oauth_scopes_to_api_methods. Finally, if you have additional questions you can reach out to an owner on your workspace who may know more about this token or its usage. Otherwise, you can reply directly to this notification - our support team is standing by and ready to help. -The team at Slack |
So we all can't use this solution any longer? |
You can use it with this workaround: |
follow the instruction to create a new stack in heroku. but when try to generate legacy token, I got this error.
How can I get the token now?
The text was updated successfully, but these errors were encountered: