[
https://issues.apache.org/jira/browse/BEAM-7190?focusedWorklogId=251040&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-251040
]
ASF GitHub Bot logged work on BEAM-7190:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/May/19 15:41
Start Date: 30/May/19 15:41
Worklog Time Spent: 10m
Work Description: lukecwik commented on issue #8597: [BEAM-7190] Enable
file based token auth for samza portable runner
URL: https://github.com/apache/beam/pull/8597#issuecomment-497376259
Note that the
[ApiServiceDescriptor](https://github.com/apache/beam/blob/de19c75062654b2b7f4a5c406acd0a0442ba1a0d/model/pipeline/src/main/proto/endpoints.proto#L31)
does have an authentication segment, would it make sense to provide this
additional information there instead of passing it around in headers?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 251040)
Time Spent: 50m (was: 40m)
> enable file system based token authentication for 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
> Assignee: Hai Lu
> Priority: Major
> Time Spent: 50m
> 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
(v7.6.3#76005)
