feat(sdk): Support custom key splits #1038
Merged
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
dmihalcik-virtru
changed the title
dmihalcik-virtru
force-pushed
the
feature/split-plan
branch
2 times, most recently
from
8890e5b
to
645cf23
Compare
dmihalcik-virtru
force-pushed
the
feature/split-plan
branch
from
53169d7
to
b715127
Compare
Implementation of opentdf/spec#32 This is a proposal to allow customizing how a client shares key data across multiple KASes. With a split, you can copy the same share to multiple providers, allowing for robustness if a given KAS is unavailable - or if a decrypting user or application does not have authorization with that KAS.
dmihalcik-virtru
force-pushed
the
feature/split-plan
branch
from
b715127
to
fe87e02
Compare
pflynn-virtru
approved these changes
Jul 2, 2024
jrschumacher
reviewed
Jul 2, 2024
patmantru
approved these changes
Jul 8, 2024
strantalis
reviewed
Jul 8, 2024
strantalis
reviewed
Jul 8, 2024
strantalis
approved these changes
Jul 10, 2024
This was referenced Jul 10, 2024
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jul 11, 2024
🤖 I have created a release *beep* *boop* --- ## [0.2.11](sdk/v0.2.10...sdk/v0.2.11) (2024-07-11) ### Features * **sdk:** Support custom key splits ([#1038](#1038)) ([685d8b5](685d8b5)) ### Bug Fixes * **core:** Autobump sdk ([#1132](#1132)) ([da9145c](da9145c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jul 11, 2024
🤖 I have created a release *beep* *boop* --- ## [0.4.11](service/v0.4.10...service/v0.4.11) (2024-07-11) ### Features * **authz:** Keycloak ERS ability to handle clients, users, and emails that dont exist ([#1113](#1113)) ([4a17f18](4a17f18)) * **core:** GetEntitlements with_comprehensive_hierarchy ([#1121](#1121)) ([ac85bf7](ac85bf7)), closes [#1054](#1054) * **sdk:** Support custom key splits ([#1038](#1038)) ([685d8b5](685d8b5)) ### Bug Fixes * **core:** Autobump service ([#1133](#1133)) ([1a1a64f](1a1a64f)) * **core:** Autobump service ([#1136](#1136)) ([baaee4d](baaee4d)) * **core:** Autobump service ([#1139](#1139)) ([7da3cb9](7da3cb9)) * **kas:** remove unused hostname check ([#1123](#1123)) ([2909700](2909700)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
elizabethhealy
added a commit
to opentdf/java-sdk
that referenced
this pull request
Aug 19, 2024
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.
Implementation of opentdf/spec#32
This is a proposal to allow customizing how a client shares key data across multiple KASes. With a split, you can copy the same share to multiple providers, allowing for robustness if a given KAS is unavailable - or if a decrypting user or application does not have authorization with that KAS.