[server] Add authorization to Remote Log & Tiering RPCs (commitRemoteLogManifest, notifyRemoteLogOffsets, lakeTieringHeartbeat)
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Motivation
**Part of umbrella issue #2007 - Phase 2: Internal RPCs**
Add authorization checks for remote log and tiering operations:
- `commitRemoteLogManifest` - CLUSTER/WRITE
- `notifyRemoteLogOffsets` - CLUSTER/WRITE
- `lakeTieringHeartbeat` - CLUSTER/WRITE
These are **internal server-to-server RPCs** that need both:
1. Authorization checks for CLUSTER/WRITE operations
2. Validation that `session.isInternal()` is true to prevent external clients from
calling internal APIs
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the server handlers for commitRemoteLogManifest, notifyRemoteLogOffsets, and lakeTieringHeartbeat, then read the existing authorization and session.isInternal checks around related internal RPCs. Done means all three operations enforce CLUSTER/WRITE authorization and reject sessions that are not internal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100