signed urls
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 181
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
At today's Pangeo meeting, we discussed the idea of using signed urls to provided unauthenticated users access to google cloud storage, specifically for reading zarr stores. I'm creating this issue to track that idea.
I found this page in the gcs docs with some helpful advice.
https://cloud.google.com/storage/docs/access-control/signing-urls-manually
How would we go about "proxying" access to a restricted bucket via signed urls? I can't quite wrap my head around it. Where would the signing happen? It couldn't happen from the user's notebook pod--it would have to happen from within some service running somewhere with enhanced credentials. Could we connect it to jupyterhub's auth? Or to our auth0 account?
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 implementation files or tests are named. Start with the linked Google Cloud Storage manual signing-URLs documentation, then investigate how a service could sign restricted-bucket requests for unauthenticated Zarr reads and how JupyterHub or Auth0 might fit. Done means an agreed, implementable design or a documented decision that this approach is out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, python
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100