You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:18 UTC
[jira] [Commented] (BEAM-7190) Enable file system based token
authentication for Samza portable runner
[ https://issues.apache.org/jira/browse/BEAM-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174729#comment-17174729 ]
Beam JIRA Bot commented on BEAM-7190:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Enable file system based token authentication for Samza portable runner
> -----------------------------------------------------------------------
>
> Key: BEAM-7190
> URL: https://issues.apache.org/jira/browse/BEAM-7190
> Project: Beam
> Issue Type: Task
> Components: runner-samza
> Reporter: Hai Lu
> Priority: P2
> Labels: stale-P2
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> For Samza and potentially other portable runners, there is a need to secure the communication between sdk worker and runner. Currently the SSL/TLS in portability is half done.
> However, after investigation we found that it's sufficient to just 1) use loopback address 2) enforce authentication and that way the communication is both authenticated and secured.
> This ticket intends to track the implementation of the solution above. More details can be found in the following PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)