Skip to content

feat(s3): wire SIGV4_HEADER_MODE config into davix params#28

Open
mgajek-cern wants to merge 1 commit into
cern-fts:developfrom
mgajek-cern:feat/27-s3-sigv4-header-mode
Open

feat(s3): wire SIGV4_HEADER_MODE config into davix params#28
mgajek-cern wants to merge 1 commit into
cern-fts:developfrom
mgajek-cern:feat/27-s3-sigv4-header-mode

Conversation

@mgajek-cern

Copy link
Copy Markdown

No effect without the paired davix build (signRequestv4 + setAwsSigV4HeaderMode).

Closes: #27
Depends-on: cern-fts/davix#149


Reviewer/s: @joaopblopes , @andrea-manzi

Following the discussion with Andrea and Joao regarding the addition of AWS SigV4 header signing for RI-SCALE (Copernicus Data Space interop), either would be suitable to review.

Read a per-endpoint boolean SIGV4_HEADER_MODE from the [S3:HOST] config groups
and forward it to davix via RequestParams::setAwsSigV4HeaderMode(), so S3 v4
requests can be signed in Authorization-header form for endpoints whose gateways
reject URL-embedded signatures (e.g. Copernicus Data Space). Resolved with the
same most-specific-group-wins precedence as ALTERNATE/REGION
(S3:HOST -> S3:HOST-no-bucket -> S3); defaults to false, so other S3 endpoints
are unchanged.

No effect without the paired davix build (signRequestv4 + setAwsSigV4HeaderMode).

Closes: cern-fts#27
Depends-on: cern-fts/davix#149
Refs: https://docs.aws.amazon.com/AmazonS3/latest/developerguide/sigv4-auth-using-authorization-header.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wire SIGV4_HEADER_MODE config into davix params

1 participant