Skip to content

adr: default kas keys for platform #2121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

strantalis
Copy link
Member

Proposed Changes

Checklist

  • I have added or updated unit tests
  • I have added or updated integration tests (if appropriate)
  • I have added or updated documentation

Testing Instructions

@strantalis strantalis requested a review from a team as a code owner April 28, 2025 15:28
@strantalis strantalis added the adr Architecture Decision Records pertaining to OpenTDF label Apr 28, 2025
@strantalis strantalis requested a review from a team as a code owner April 28, 2025 15:35
Comment on lines 109 to 114
| Column | type |
| ------- | ------------- |
| id | uuid (string) |
| key_id | string |
| ..... | ..... |
| default | bool |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this documenting the change to the new asymmetric keys table?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah and maybe I should just remove this because it gets into implementation details.

| key_id | string |
| ..... | ..... |
| default | bool |

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The default key and KAS for ZTDF and NanoTDF served by the well-known configuration will be a combination of policy and config (dependent on the in-flight Key Management work).
The config will specify the `kid` for each key and the public...

Do you think we should have the well-known config for the default KAS point to one of the registered KASes in policy, which would have the added benefit of ensuring the well-known KAS uri has been allowListed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be the idea if we added a default bool column to the kas keys table. This way on startup we can pull that info automatically and add it to wellknown.

Co-authored-by: Jake Van Vorhis <83739412+jakedoublev@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adr Architecture Decision Records pertaining to OpenTDF
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants