-
Notifications
You must be signed in to change notification settings - Fork 290
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
fix (kms): properly reconcile DEKs for existing scopes #1976
Conversation
When new DEKs are added to boundary we need to ensure that the keys for existing scopes are reconciled. This fix should address: #1856
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.
I reserve business logic judgment as I don't feel I have enough context.
// | ||
// NOTE: don't add an audit key here since it can only be created in | ||
// the global scope. | ||
KeyPurposeOidc, |
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.
Are we already creating OIDC DEKs for non-global/org scopes? If not we may want a check here since this will be called with all scopes from the controller New function.
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.
We are calling kms.CreateKeysTx(...)
every time we create a new scope.
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.
Approved pending a check on if oidc keys are supposed to be getting created in project scopes.
When new DEKs are added to boundary we need to ensure that the keys
for existing scopes are reconciled.
This fix should address:
#1856