This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Pass Slack OAuth redirect_uri
query params when present
#329
Labels
Comments
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Jul 25, 2016
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Jul 27, 2016
@peterswimm any thoughts on this? Our app needs a solution to handle oauth flows in different ways, right now I'll have to use a hard fork. Wondering if you see the value in this. I'd imagine all Slack apps would want to behave this way, but maybe it's only me? |
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 8, 2016
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 14, 2016
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 24, 2016
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 25, 2016
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 25, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 25, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 29, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Aug 31, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Sep 8, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Sep 22, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Oct 13, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
sundeepgupta
added a commit
to sundeepgupta/botkit
that referenced
this issue
Oct 27, 2016
Allow passing of custom params into the Slack auth flow. The custom params are passed through the flow and are passed back into the `create_user` and `update_user` events. howdyai#329
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The use case is a user issues a slash command, but we can't process their slash command because we don't have their access token yet. So we save the command in our server and respond with an auth link. The user goes through the auth flow and now that we have a token, we wan't to process their original command.
Before Botkit, I was doing this be adding a
command=99
query param onto theredirect_uri
and I'd check for it when Slack POSTed back with the user's token. It worked nicely.With Botkit, It looks like I'd have to manually process the POST request. Perhaps this could be passed into the
create_user
event?The text was updated successfully, but these errors were encountered: