Skip to content
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

Conversation

paullatzelsperger
Copy link
Member

@paullatzelsperger paullatzelsperger commented Jan 25, 2024

What this PR changes/adds

Adds a management API for KeyPairResources, that allows to:

  • find by ID or participant ID
  • rotate a key
  • revoke a key
  • add a key pair

Why it does that

managing key pairs

Further notes

  • adapts to latest upstream changes, specifically the SqlOperatorTranslator and changes to the PresentatinQueryMessage and PresentationResponseMessage

Linked Issue(s)

Closes #235

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

@paullatzelsperger paullatzelsperger added enhancement New feature or request api labels Jan 25, 2024
@paullatzelsperger paullatzelsperger force-pushed the feat/235_add_keypairresource_managementapi branch 2 times, most recently from 254e897 to 8170aa2 Compare January 26, 2024 09:36
@paullatzelsperger paullatzelsperger force-pushed the feat/235_add_keypairresource_managementapi branch 3 times, most recently from a111de4 to c44a3cb Compare January 28, 2024 10:15
@paullatzelsperger paullatzelsperger force-pushed the feat/235_add_keypairresource_managementapi branch from c44a3cb to 5d2f429 Compare January 28, 2024 10:17
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.",
Copy link
Contributor

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

Copy link
Member Author

@paullatzelsperger paullatzelsperger Jan 29, 2024

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?

Copy link
Contributor

@jimmarino jimmarino Jan 29, 2024

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.

@paullatzelsperger paullatzelsperger merged commit 2536037 into eclipse-edc:main Jan 29, 2024
13 of 14 checks passed
@paullatzelsperger paullatzelsperger deleted the feat/235_add_keypairresource_managementapi branch January 29, 2024 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create KeyPairResourceManagementApi
3 participants