Implement Discord OAuth Middleware #125
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
godoc reference preview ready ✨
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Everything behind a
v1/route now requires theAuthorization: Bearer <access_token>header to access. You can setENV=developmentin.envand useBearer dev-tokento bypass this for now.To test the OAuth flow, set
ENV=production.The easiest way to test the Auth out is to check out PR #126 locally and use the command
acmcsuf-cli events get. This is the only command/subcommand that's using the new OAuth flow. Otherwise running the flow manually is a little annoying.