Support multiple redirection URI for OAuth 2.0 clients
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
I'd like to get rid of google oauth integration I use in oauth2_proxy (https://github.com/oauth2-proxy/oauth2-proxy)
Currently I use oauth2_proxy as a proxy (ahem) for multiple services hosted behind the same domain name (me.toto.com, you.toto.com,hello.toto.com) and I use only one client id/secret, and add multiple "Authorized redirect URIs" in google console
Describe the solution you'd like
The same thing in google console, i.e. being able to specify multiple redirection URI for OAuth 2.0 clients
Describe alternatives you've considered
Maybe we could have some kind of wildcards? https://*.toto.com
One solution for me would be to run one instance of oauth2_proxy behind each service, and have a pair client_id/secret for each services, not really usable right now unfortunately
Additional context
Thanks for your amazing work, I'm getting each day a little bit more degoogleized
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
No files, tests, or entry points are named. Start by locating the OAuth 2.0 client configuration in the Nextcloud server repository and trace how authorized redirect URIs are handled; done means the requested multiple-URI behavior works without requiring separate client credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100