spring-projects / spring-projects/spring-security
SEC-3026: simpSubscribeDestMatchers should match also the disconnect event
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Alex (Migrated from SEC-3026) said:
In my websocket security I've a rule similar to the usual one:
bq. .simpSubscribeDestMatchers("/topic/**").permitAll()
this is nice because it allows any client to subscribe to public queues, but it has a problem: it does not allow them to unsubscribe.
So another method with a tentative name like simpUnsubscribeDestMatchers would be needed for that, or maybe better a method that can match both subscribe and unsubscribe type of messages in order to apply the security policy
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 tracing the WebSocket security configuration entry point that exposes simpSubscribeDestMatchers and how it handles subscribe, unsubscribe, and disconnect messages. Resolve whether the intended behavior covers unsubscribe, disconnect, or both, then verify that the chosen matcher API applies the public-destination policy without weakening other message rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100