Oauth endpoints not created
See original GitHub issueDescription
I followed the documentation here, and I cannot seem to get the oauth module working as is specified. In the docs, it says it sets up the following endpoints:
slack/oauth_redirect
slack/install
However, it appears neither is actually configured. I followed the default config (subbing in my own configs, of course), and have yet to see it return anything other than a cannot GET...
message. Am I perhaps doing something wrong? Are the docs out of date or perhaps showing for a future release? I would love some guidance here.
What type of issue is this? (place an x
in one of the [ ]
)
- bug?
- enhancement (feature request)
- question
- documentation related
- testing related
- discussion
Requirements (place an x
in each of the [ ]
)
- I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
- I’ve read and agree to the Code of Conduct.
- I’ve searched for any related issues and avoided creating a duplicate issue.
Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 2.2.3
node version: 14.4
OS version(s): Linux pop-os 5.4.0-7634-generic #38~1592497129~20.04~9a1ea2e-Ubuntu SMP Fri Jun 19 22:43:37 UTC x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce:
- Follow the docs
- Attempt to set up redirect
- Try to use oauth to authenticate
- Cry 😢
Expected result:
Authentication to work
Actual result:
Great sadness
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Are you defining your own
receiver
? If so, the OAuth options (clientId
,clientSecret
,stateSecrect
, etc) need to be passed toExpressReceiver
instead.@stevengill That seems to have worked flawlessly, to anyone copying my config, I also had to remove the
token
field. Very sorry about this mistake, thanks so much for taking the time to review my error.