spring-projects / spring-projects/spring-security
Concurrency Control Broken when HttpSession.changeSessionId then SessionRegistry.registerNewSession
Open
Nobody has claimed this yet.
in: web
type: bug
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
If Concurrency Control is enabled and SessionRegistry.registerNewSession is invoked and then HttpSession.changeSessionId the concurrency control fails because the stored session is not updated.
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 reproducing the sequence described: register a new session through SessionRegistry, then call HttpSession.changeSessionId with concurrency control enabled. Trace how the registry stores and updates the session, and consider the issue done when the stored session reflects the changed ID and concurrency control continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100