spring-projects / spring-projects/spring-security
SupplierClientRegistrationRepository for reactive stack
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Expected Behavior
When starting spring boot application with reactive stack (e.g. spring cloud gateway), it would be useful to not fail if IdP is not available at the boot time.
Current Behavior
Currently if IdP is not available and we use provider's issuer-uri property, application won't start.
Context
For non reactive stack there's already SupplierClientRegistrationRepository.
related issues
spring-boot
spring-security
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 examining the existing SupplierClientRegistrationRepository for the non-reactive stack and trace how issuer-uri is handled for the reactive stack. Use the related Spring Boot and Spring Security issues for context; done means a reactive application can start when the identity provider is unavailable at boot while retaining client registration behavior once it is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100