martin-traverse opened a new issue, #34595:
URL: https://github.com/apache/arrow/issues/34595

   ### Describe the enhancement requested
   
   Hello,
   
   It seems that federated / external identities are not supported in the Arrow 
GcsFileSystem implementation? It would be great to support this. I'm using it 
in CI with GitHub as an IdP as per the 
[instructions](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform)
 and it works great for the Google CLI tools.
   
   I'm not sure how this is implemented, is there a standard library from 
Google that can just be linked / updated? The federated auth mechanism creates 
a regular Google application creds file, with the "type" set as 
"external_account". Is there an easy (ish) way to bring this in if the Google 
libs handle the different standard credential types? Or is that wishful 
thinking on my part?
   
   I'm interested in the Python component but guess this would come to other 
languages that use the same underlying code if it was added.
   
   Here is the stack trace from Arrow:
   
    File "pyarrow/_fs.pyx", line 571, in pyarrow._fs.FileSystem.get_file_info
     File "pyarrow/error.pxi", line 144, in 
pyarrow.lib.pyarrow_internal_check_status
     File "pyarrow/error.pxi", line 100, in pyarrow.lib.check_status
   pyarrow.lib.ArrowInvalid: google::cloud::Status(INVALID_ARGUMENT: Permanent 
error GetObjectMetadata: Could not create a OAuth2 access token to authenticate 
the request. The request was not sent, as such an access token is required to 
complete the request successfully. Learn more about Google Cloud authentication 
at https://cloud.google.com/docs/authentication. The underlying error message 
was: Unsupported credential type (external_account) when reading Application 
Default Credentials file from [/path/to/credentials.json].). Detail: [errno 22] 
Invalid argument
   
   ### Component(s)
   
   Python


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to