Authenticating via Interoperable storage access keys
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 181
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
Hi,
I'm working on a project that implements connections to S3 via the super simple aws_access_key_id, aws_secret_access_key variables and I'd like to extend the functionality to include GCS access too.
GCS has similar functionality via their interoperability API but I can't seem to figure out how to use this to authenticate the connection to my bucket. Really, what I want to be able to do is pull the access key and secret from a file and use that to authenticate, without using the 'browser' token and caching. Is that possible from the current implementation?
Best,
Zain
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by tracing gcsfs's current authentication flow and how it handles browser tokens and cached credentials, then investigate GCS interoperability access keys. Done means a connection can authenticate from a file containing the access key and secret without browser authentication or token caching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100