spring-projects / spring-projects/spring-security
Consider a `ReactiveMaximumSessionExceededHandler` that performs `POST /logout`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Similar to OidcBackChannelServerLogoutHandler. Such implementation would forge a POST /logout with the session id and needed attributes, like the CSRF token. It would have the advantage of invoking the cleanup needed during a regular logout, instead of just removing the session from the WebSessionStore like the InvalidateLeastUsedReactiveMaximumSessionsExceededHandler does.
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 reading OidcBackChannelServerLogoutHandler and InvalidateLeastUsedReactiveMaximumSessionsExceededHandler to understand the existing logout and session-removal paths. Determine how a ReactiveMaximumSessionExceededHandler could issue POST /logout with the session id and required attributes, including the CSRF token, while preserving regular logout cleanup. Done means the new handler invokes the normal logout cleanup rather than only removing the session from WebSessionStore.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100