Skip to content

Conversation

@mkleene
Copy link
Contributor

@mkleene mkleene commented Oct 7, 2024

This allows for use cases where we need to examine the policy to see if we should decrypt.

When we send the policy to KAS to unwrap we know that KAS will validate the policy binding so that
the policy we used to determine access must be correct.

Also use a single static gson instance to clarify which options (zero now) we are using for serialization
in the Manifest

@mkleene mkleene marked this pull request as ready for review October 7, 2024 15:53
@mkleene mkleene requested review from a team as code owners October 7, 2024 15:53
@mkleene mkleene changed the title fix(sdk): deserialize policy objects feat(sdk): deserialize policy objects Oct 7, 2024
@mkleene mkleene merged commit 39582f3 into main Oct 9, 2024
5 checks passed
@mkleene mkleene deleted the feature/deserialize-policy-object branch October 9, 2024 12:59
pflynn-virtru pushed a commit that referenced this pull request Oct 9, 2024
🤖 I have created a release *beep* *boop*
---


<details><summary>0.7.3</summary>

## [0.7.3](v0.7.2...v0.7.3)
(2024-10-09)


### Features

* **sdk:** deserialize policy objects
([#179](#179))
([39582f3](39582f3))
</details>

---
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>
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.

4 participants