-
Notifications
You must be signed in to change notification settings - Fork 25
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
feat: add Management API for KeyPairResources #239
feat: add Management API for KeyPairResources #239
Conversation
254e897
to
8170aa2
Compare
a111de4
to
c44a3cb
Compare
c44a3cb
to
5d2f429
Compare
void rotateKeyPair(String id, KeyDescriptor newKey, long duration, SecurityContext securityContext); | ||
|
||
@Tag(name = "KeyPairResources Management API") | ||
@Operation(description = "Revokes (=removes) a particular key pair, identified by their ID and create a new successor key.", |
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 should have the option of rotating and revoking a key without generating successor keys. This could be a non-default case
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, I initially had it that way, but I couldn't figure out a use case where "phasing out" a key without a successor would be needed. Note that revoking does not require a successor, even now.
should I make the successor optional also when rotating?
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.
Yes, that would be good.
What this PR changes/adds
Adds a management API for
KeyPairResources
, that allows to:Why it does that
managing key pairs
Further notes
SqlOperatorTranslator
and changes to thePresentatinQueryMessage
andPresentationResponseMessage
Linked Issue(s)
Closes #235
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.