feat: implement CloudFront signed-cookie minting - #168
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_mint_cloudfrontsigning (Piece 1 of auth: implement CloudFront signed-cookie minting for ambient Zarr access #166) — build a CloudFront custom policy (Resource: "{url}/*"per-dataset scope,DateLessThan= TTL epoch), RSA-SHA1 sign it with the PEM key, apply CloudFront's URL-safe base64. Replaces the"TODO"placeholders.cryptographyexplicitly (was only transitive viapyjwt[crypto]).HTTP_TOKENpath andmint_credentialsdispatch untouched.Test Plan
test_credentials.py(9 passed) — the happy-path test RSA-SHA1-verifies the signature against the public key, proving CloudFront would accept it; plus policy-shape, expiry-range, and missing/invalid-key error testsPiece 1 of #166 (signing only). Ambient
Set-Cookiedelivery (.cbioportal.org), frontendcredentials: 'include', and the CloudFront key-group/distribution infra are separate follow-ups — this does not change prod behavior on its own.