Client-side encryption no longer alters user-provided metadata #25133
Conversation
This file contains 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
…o storage/fix/encryptionmedatata
jaschrep-msft
requested review from
amishra-dev,
amnguye,
kasobol-msft,
seanmcc-msft and
tg-msft
as code owners
ghost
added
the
seanmcc-msft
approved these changes
Nov 4, 2021
|
Resolves #24801 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Client-side encryption adds a field to blob metadata on upload, containing all the encryption metadata so the SDK knows how to decrypt on download. Previously, it added the field to the caller-provided
IDictionary<string, string>before uploading that dictionary as metadata, but the SDK should not modify caller-provided objects.The dictionary is now cloned when using client-side encryption, and the metadata is added to the clone.