oauth failing on deployment for github
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Github
No support for multiple callback URLs as of now.
> The bad news is we can't insert more than one callback to GitHub OAuth setting.
> Good news is that we can use multiple callback sub-url under our callback url, then you can redirect(proxy) it to any callback url that you want.
Refer to the [Stackoverflow Question](https://stackoverflow.com/questions/35942009/github-oauth-multiple-authorization-callback-url)
---
One quick fix is having 2 different GitHub OAuth Apps, one for prodcution and other for localhost. But that's the last resort available.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or concrete entry points are named. Start by locating the GitHub OAuth callback configuration and deployment settings, then verify localhost and production callback behavior; done means deployment OAuth succeeds without requiring separate applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, github, python
- Domain
- authentication, backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100