spring-projects / spring-projects/spring-security
SEC-3069: ConcurrentSessionFilter should respond with 401 or 403 instead of 200, when session was expired
Open
Nobody has claimed this yet.
in: core
type: enhancement
type: jira
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Sanjaya Kumar Patel (Migrated from SEC-3069) said:
When coding a REST API for some client, the client would expect an error response if a login session was expired due to a concurrent session being opened somewhere else. ConcurrentSessionFilter is used for sending the message to the client. But the response returns 200 instead of 401 or 403.
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 ConcurrentSessionFilter and trace how it handles an expired session during concurrent-session invalidation. Reproduce the REST API response described in the issue and verify that the expired-session case returns 401 or 403 instead of 200.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100