Document use of multiple OAuth redirect URLs
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 116
- Forks
- 51
- Avg merge
- 1h 25m
- Merged PRs (30d)
- 1
Description
The developer console indicates that applications can specify multiple redirect URLs, which could be particularly useful for developing on localhost and running in production on a public domain.
I have attempted to use URLs in the following formats:
http://localhost:8080/receive, https://prod.foo.com/receive
http://localhost:8080/receive,https://prod.foo.com/receive
http://localhost:8080/receive; https://prod.foo.com/receive
http://localhost:8080/receive;https://prod.foo.com/receive
None of these appear to have worked so far. It would be great to get some documentation on what format these URLs should be in.
Contributor guide
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
Start by verifying the accepted format for multiple OAuth redirect URLs in the developer console and the existing public API documentation. Document the supported format and the localhost/production examples from the issue, with the relevant documentation updated so developers can configure both environments.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100