You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/05 00:18:00 UTC
[jira] [Commented] (BEAM-14319) Dataflow runner not working with Workload Identity federation ("external_account")
[ https://issues.apache.org/jira/browse/BEAM-14319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549960#comment-17549960 ]
Danny McCormick commented on BEAM-14319:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/21530
> Dataflow runner not working with Workload Identity federation ("external_account")
> ----------------------------------------------------------------------------------
>
> Key: BEAM-14319
> URL: https://issues.apache.org/jira/browse/BEAM-14319
> Project: Beam
> Issue Type: Improvement
> 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)