spring-cloud / spring-cloud/spring-cloud-gateway
SCG as an oauth2 client + proxy to the IdP at the same time
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Hi team
Is it possible for SCG to act as an oauth2 client and hide/proxy it's own IdP at the same time ?
For internally hosted IdP (spring-auth-server, keycloak), if we don't want to expose them directly,
when SGC is acting as an oauth client it can't proxy IdP because it won't be able to call /.well-known through itself
(it can be solved by a secondary stateless gateway just for IdP),
but is there any way to make this possible if we are trying to have a unique scalable SGC
maybe defer the call to /.well-known until routing has started
thx in advance
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
The issue names no files, tests, or entry points. Start by tracing Spring Cloud Gateway's OAuth2 client discovery and proxy routing behavior, especially access to /.well-known, then determine the required design for one gateway to handle both roles; done would mean an implemented and tested supported configuration or a documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100