[
https://issues.apache.org/jira/browse/FLINK-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019632#comment-16019632
]
Chesnay Schepler commented on FLINK-6454:
-----------------------------------------
We could also think about making the job-submission parameter more granular;
for example to forbid uploading jars but allow running them, the jars to run
would be placed in the {{web.upload.dir}} directory by an administrator of some
sort.
> Add more permission settings to the web UI
> ------------------------------------------
>
> Key: FLINK-6454
> URL: https://issues.apache.org/jira/browse/FLINK-6454
> Project: Flink
> Issue Type: Sub-task
> Components: Webfrontend
> Reporter: Stephan Ewen
> Labels: starter
>
> Currently, the web UI allows all users with access everything. Only job
> upload has a separate permission setting.
> We should generalize that to more aspects of the UI, such as cancelling jobs,
> accessing logs, or accessing metrics.
> We could add a flag for each feature (enable / disable).
> Alternatively, we can add an access level to the UI:
> # view job only (dag, timeling, checkpoint stats)
> # view dag and metrics + logs
> # view dag/metrics/logs plus allow stop / cancel / savepoint
> # allow all (before plus submitting new jobs)
> The second options is less flexible, but more compact to configure.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
