Need S3PROXY_AUTHORIZATION Documentation in Wiki

Aperta
  • Qualcosa non va?
#472 3 commenti 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
aws, docker
Ambito
authentication, documentation

Direzione di ricerca

Start with the S3Proxy wiki and the documented settings for S3PROXY_AUTHORIZATION, S3PROXY_IDENTITY, and S3PROXY_CREDENTIAL; compare the documented behavior with the AWS S3 backend setup described in the issue. Done means the wiki explains what the authorization setting and credentials do, including why clients and S3Proxy may use separate credentials.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I started off testing S3Proxy with Authorization set to none and everything worked great. However, as I roll this out to production I want to secure the server. I see that the default value for the docker S3PROXY_AUTHORIZATION ENV is "aws-v2-or-v4". I'm rather confused as to what this means and I can't find any explanation in the wiki.

I currently have S3Proxy setup to connect to AWS S3 with JCLOUDS_PROVIDER=aws-s3. At first I thought that setting S3PROXY_AUTHORIZATION to "aws-v2-or-v4" would mean that my AWS SDK s3Client would need to pass along valid AWS Access Key and Secret Keys and that S3Proxy would authenticate those keys with AWS. That did not work. Then I set the same valid AWS keys in S3Proxy using the ENVs S3PROXY_IDENTITY and S3PROXY_CREDENTIAL. That did work.

While that worked, I didn't quite understand why both my client and the S3Proxy server would need valid AWS credentials. The client should have been enough. Then I changed the client keys to randomly created username and password similar to s3proxyuser/password123456. I set the same credentials for S3PROXY_IDENTITY and S3PROXY_CREDENTIAL on S3Proxy. And to my surprise it worked!

Are S3PROXY_IDENTITY and S3PROXY_CREDENTIAL used to hardcode a username and password for S3Proxy? I think that makes sense but it would be helpful if the wiki could fully document the functionality.

Lingua principale
Java
Stelle
2.4k
Fork
289
Merge medio
12h 52m
PR unite (30g)
22

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di gaul/s3proxy

Tutte le issue di gaul/s3proxy

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.