[
https://issues.apache.org/jira/browse/FLINK-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636444#comment-15636444
]
ASF GitHub Bot commented on FLINK-3930:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/2425#discussion_r86548851
--- Diff: docs/setup/yarn_setup.md ---
@@ -134,6 +140,14 @@ Flink on YARN will only start all requested containers
if enough resources are a
some account also for the number of vcores. By default, the number of
vcores is equal to the processing slots (`-s`) argument. The
`yarn.containers.vcores` allows overwriting the
number of vcores with a custom value.
+### Service Authorization using Secure Cookie
+
+If service authorization for the cluster components (Akka, Blob Service,
Web UI) is enabled, you could pass the secure cookie value as command line
argument (-k or --cookie) instead of hardcoding the value in Flink
configuration file.
--- End diff --
I would link to the main security docs from here.
A crucial thing to point out here is that when users use this with YARN
sessions, all jobs running in that session will use the same cookie. The cookie
is a "per-cluster" or "per-processes" parameter.
Please add that for proper security between jobs, jobs should be submitted
individually, not via a Flink Yarn Session.
> Implement Service-Level Authorization
> -------------------------------------
>
> Key: FLINK-3930
> URL: https://issues.apache.org/jira/browse/FLINK-3930
> Project: Flink
> Issue Type: New Feature
> Components: Security
> Reporter: Eron Wright
> Assignee: Vijay Srinivasaraghavan
> Labels: security
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> _This issue is part of a series of improvements detailed in the [Secure Data
> Access|https://docs.google.com/document/d/1-GQB6uVOyoaXGwtqwqLV8BHDxWiMO2WnVzBoJ8oPaAs/edit?usp=sharing]
> design doc._
> Service-level authorization is the initial authorization mechanism to ensure
> clients (or servers) connecting to the Flink cluster are authorized to do so.
> The purpose is to prevent a cluster from being used by an unauthorized
> user, whether to execute jobs, disrupt cluster functionality, or gain access
> to secrets stored within the cluster.
> Implement service-level authorization as described in the design doc.
> - Introduce a shared secret cookie
> - Enable Akka security cookie
> - Implement data transfer authentication
> - Secure the web dashboard
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
