[
https://issues.apache.org/jira/browse/KYLIN-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123747#comment-18123747
]
ASF subversion and git services commented on KYLIN-6118:
--------------------------------------------------------
Commit f59f1e74c312bee5eebe638e227665111498d1cd in kylin's branch
refs/heads/kylin5 from Li Yang
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f59f1e74c3 ]
KYLIN-6118 require service token on streaming internal RPC endpoints
The streaming progress-report and dataflow RPC handlers (spark, stats,
segment add/update/delete, and layout update) are public in the security
chain and relied only on the optimistic jobExecutionId checkToken, which
is not authentication. Extend the internal service-token gate to these
handlers and have the streaming sender attach the deployment-scoped
credential, so streaming jobs keep reporting without configuration.
> Potential unauthorized internal job-report RPC issue
> ----------------------------------------------------
>
> Key: KYLIN-6118
> URL: https://issues.apache.org/jira/browse/KYLIN-6118
> Project: Kylin
> Issue Type: Bug
> Reporter: liyang
> Priority: Major
>
> Several internal job progress-report RPC operations are exposed on the public
> API port and are marked as public in the security chain, but they do not
> verify the caller identity or authorization. A caller that knows a running
> job identifier and its running-start value can submit forged progress, error,
> stage-status, and wait/run-time updates to job metadata.
> The affected operations are the internal job progress-report RPC endpoints
> under the job controller.
> Fix direction: require either an authenticated global administrator or a
> valid internal service credential on these internal RPC operations, and have
> the internal job-progress reporter send the credential.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
