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/28 17:59:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Kenneth Knowles updated BEAM-14319:
-----------------------------------
    Summary: Dataflow runner not working with Workload Identity federation ("external_account")  (was: Apache Beam not working with Workload Identity federation)

> 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)