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

Invitation fails with Failed! missing_scope #8

Closed
kevin-lee opened this issue Sep 19, 2015 · 8 comments
Closed

Invitation fails with Failed! missing_scope #8

kevin-lee opened this issue Sep 19, 2015 · 8 comments

Comments

@kevin-lee
Copy link

I tested the invitation feature with a few different email addresses but none has succeeded.

I get Failed! missing_scope when using this app and the following result if I use curl command provided in the README.md.

{"ok":false,"error":"missing_scope","needed":"admin","provided":"identify,read,post,client"}

I've already checked https://api.slack.com/tokens page and it says that the token has admin scope.

@kevin-lee
Copy link
Author

I'm not quite sure but it probably has something to do with Slack API itself.
https://twitter.com/SlackAPI/status/644943274558533632

winston added a commit to rubysg/rubysg-reboot that referenced this issue Sep 19, 2015
… my email so that people can still drop me email to get access.

We are using a secret api as documented on https://levels.io/slack-typeform-auto-invite-sign-ups/,
however there are problems like this outsideris/slack-invite-automation#8.
@kevin-lee
Copy link
Author

Unfortunately, it's official now. 😞 Slack says it's an undocumented method so not supported. They're working on an alternative to the method but has no firm timeline for its release. sigh... 😞 I'm not sure what else can be done at this point. :(

@ghost
Copy link

ghost commented Sep 20, 2015

I hit the same problem - the code used to work but, when I saw this issue, I checked and found the same problem. Seems as if the tokens issued at https://api.slack.com/web#auth don't have the required "admin" in their scope list.

There is a work around, but I'm not sure if it abides by Slack's terms of service. With a browser, log into Slack and go through the workflow to send an invite to someone. Use the browser's "inspect element" to look at the request when you hit the invite button. If you look in the "form data", you should see a token. For me, this token works with the slack-invite-automation code.

@outsideris
Copy link
Owner

@hackscribble Yes, you are right. I fix it in local. I will update it soon.

@kevin-lee
Copy link
Author

I can confirm that it's fixed. It works well with the admin key not the owner one.
@outsideris, thanks a lot!

@ivanoats
Copy link

How do we get the admin key instead of the owner one? Is there a URL to visit?

Thanks for fixing this BTW 😀

@outsideris
Copy link
Owner

@ivanoats In /admin, you should make any user as admin. Then you sign in as that user and generate the token.

@lpommers
Copy link

lpommers commented Jun 21, 2016

I just saw this issue again with an admin token... has this resurfaced for anyone else?

Edit: I had to ask for both admin and client in the scope when doing oauth

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

4 participants