spring-projects / spring-projects/spring-session
Provide & auto-configure an `OidcSessionRegistry` impl for Back-Channel Logout in distributed environments
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
Expected Behavior
When using Spring Session with Spring Boot, I'd expect Back-Channel Logout to work out of the box. This would require a compatible OidcSessionRegistry in the application context.
Current Behavior
The only OidcSessionRegistry provided by Spring Security is InMemoryOidcSessionRegistry which isn't compatible with distributed OAuth2 clients.
Context
I'm using spring-cloud-gateway-mvc configured with oauth2Login, the TokenRelay= filter, and Back-Channel Logout. To achieve high availability of k8s deployments, I'd like to have a minimum of two instances running in parallel. Unfortunately, for now, Back-Channel Logout won't work in this configuration.
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 with the Spring Security OidcSessionRegistry and InMemoryOidcSessionRegistry entry points, then review how Spring Boot auto-configuration creates application-context beans for Spring Session. Done means a compatible registry is provided automatically so Back-Channel Logout works with multiple distributed application instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes, spring, spring-boot
- Domain
- authentication, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100