`EVT_NODE_JOINED` Event security context is wrong in listener
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 1.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
```kotlin
// this service deployed by all permission subject server node
class DeploySyncServiceImpl : DeploySyncService {
override fun execute() {
// listen client node joined
ignite.events().localListen(object : IgnitePredicate {
override fun apply(e: DiscoveryEvent): Boolean {
// this not local node security context
ignite.context().security().withContext(ignite.cluster().localNode().id()).use {
// must use `withContext` switch to local node security context
}
return true
}
}, EventType.EVT_NODE_JOINED)
}
}
```
Contributor guide
Research direction
Start with the DeploySyncServiceImpl EVT_NODE_JOINED listener shown in the issue and trace how the listener obtains its security context. Done means the listener executes under the local node's security context, matching the withContext usage described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- distributed-systems, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100