Skip to content

Conversation

@dmihalcik-virtru
Copy link
Member

@dmihalcik-virtru dmihalcik-virtru commented Aug 14, 2024

  • During encrypt autoconfigure, load any KAS keys found in the policy service's Kas Registry that are associated with grants
  • These are then used to wrap any key access objects
  • Adds a bats test that demonstrates loading a key from a KAS that is offline

Deferred to not block releases until everything is bumped
Lots of things are declared in the sdk package, so this is easier than factoring shared items into a helper package that would otherwise introduce bidirectional package deps between sdk (root) and autoconfigure (internal) packages
- Lets the SDK load kas keys from the policy service
- This was removed/unsupported before, since the SDK requires Key IDs, but the service previously did not store them
- Adds a sample round trip that loads a key from a non-existant KAS to validate that the SDK doesn't call out when the key is loaded into the policy service
@dmihalcik-virtru dmihalcik-virtru force-pushed the feature/plain-text-alg-not-enum branch from 8d471a5 to 19ced97 Compare August 15, 2024 21:29
@dmihalcik-virtru dmihalcik-virtru changed the title Feature/plain text alg not enum feat(sdk): Lets SDK use PublicKeys from policy service Aug 15, 2024
@github-actions

This comment has been minimized.

1 similar comment
@github-actions
Copy link
Contributor

Warning

This pull request does not reference any issues. Please add a reference to an issue in the body of the pull request description.

@dmihalcik-virtru
Copy link
Member Author

Wrong branch. Use #1346 instead

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.

2 participants