-
Notifications
You must be signed in to change notification settings - Fork 17
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
base: main
Are you sure you want to change the base?
Conversation
| Column | type | | ||
| ------- | ------------- | | ||
| id | uuid (string) | | ||
| key_id | string | | ||
| ..... | ..... | | ||
| default | bool | |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 | | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
There was a problem hiding this comment.
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>
Proposed Changes
Checklist
Testing Instructions