-
Notifications
You must be signed in to change notification settings - Fork 27
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
invalid_auth #24
Comments
Actually let me be clear. When I run the importer I get: GetTeamInfo: invalid_auth. When I used docker-compose up slackarchive-bot I get: |
The importer should be used to import archives from zip: https://github.com/dutchcoders/slackarchive-import But invalid_auth sounds like an invalid Slack API token. |
@nl5887 is correct, it's an invalid API token. This isn't documented, but you need to go to https://api.slack.com/apps and create a new app for your workspace. Following that, set the following configuration:
|
I had a similar issue, I was using the App's verification token, instead I should've been using the chatbot's user oath token. I then went to https://api.slack.com/apps, selected my app, and then went into the "OAuth & Permissions section", then I used the "Bot User OAuth Access Token" instead and voila!
|
I cannot for the life of me figure out what auth keys I need to make this application work. I followed the instructions to the T and still I keep getting auth errors for both slackarchive and slackarchive-bot. Am I supposed to be getting these keys from somewhere else or just making them up as I go along? I tried both using random keys as well as using my slack OAuth keys and form some reason nothing works. Has anyone else figure this out?
The text was updated successfully, but these errors were encountered: