You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/04/21 18:04:00 UTC
[jira] [Commented] (BEAM-14319) Apache Beam not working with Workload Identity federation
[ https://issues.apache.org/jira/browse/BEAM-14319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525917#comment-17525917 ]
Kenneth Knowles commented on BEAM-14319:
----------------------------------------
We have some work in progress to support impersonation, but this goes beyond that. I don't know what will be required to make sure this works. Pinging [~Ryan.Thompson] just FYI.
> Apache Beam not working with Workload Identity federation
> ---------------------------------------------------------
>
> Key: BEAM-14319
> URL: https://issues.apache.org/jira/browse/BEAM-14319
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Affects Versions: 2.37.0
> Environment: Test
> Reporter: Subir Chandra Ghosh
> Priority: P2
>
> Hi Team,
> I am not able to use DataflowRunner with Apache Beam as it seems not supporting
> "external_account" in the type field of credential json file fot GCP authentication to Dataflow service with Workload Identity Federation.
>
> The error message says it only supports "service_account" and "authorized_user".
--
This message was sent by Atlassian Jira
(v8.20.7#820007)