CORE-15939: NOT FOR REVIEW - Add support for Rekey and Rewrap bus processors, add REST APIs #4578
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anien
changed the title
anien
force-pushed
the
anna/CORE-15939-add-rest-api-and-processor
branch
from
6df89fa to
b6582a4
Compare
…rker (#4820) HTTP RPC server integration into the Crypto processor. Allows Crypto processor to receive HTTP external event requests sent from the flow engine. Client integration will come later.
anien
force-pushed
the
anna/CORE-15939-add-rest-api-and-processor
branch
from
5a201ea to
14ec682
Compare
Description: used more generic name for cross version testing cluster added ability to define notary service name when onboarding notaries
CORE-16242, CORE-17822 - Integration with release branch
Adds the state status key to flow mapper state metadata and populates it with the current state. The metadata key is used by the mapper cleanup logic to ensure that mapper states are removed.
…point (#4889) Adds session timeout to the metadata stored alongside the checkpoint. Session timeout is implemented using the state storage lookup mechanism, which requires the metadata to be populated with the session timeout key. The earliest timestamp of session expiry for currently open sessions is the value assigned to this property.
During vNode creation and upgrade.
Adds a route for flow events to the flow worker event mediator.
CORE-17627, CORE-17388, CORE-17882 - integration with release
…PC (#4885) This PR adds a new implementation of MessagingClient, RPCClient, handling synchronous calls to the Corda workers via RPC/HTTP with configurable retries. Includes also a small bug-fix for the task manager. --------- Co-authored-by: Miljenko Brkic <[email protected]>
Adds an integration test for mapper cleanup. Also addresses a small bug where the key for the cleanup event was not serialized correctly.
CORE-16181 Implementing RPC client, routing external events through RPC (#4885)
…or the config required for publisher
…e to a response topic
…esource, update tests
…contains key for rotation
dickon
force-pushed
the
anna/CORE-15939-add-rest-api-and-processor
branch
from
6e4c6b0 to
640750e
Compare
|
Jenkins build for PR 4578 build 29 Build Successful: |
|
I've been through this to some extent and I think it's ready to go to the feature branch. Unfortunately to get it working I had to add a few commits of my own, which we'll need to get reviewed at some point. Since it is DRAFT and green at the time of writing I can't merge the PR so I'll simply force-push the head to the feature branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds two building blocks for key rotation
CryptoRekeyBusProcessorhandles messages coming from the REST Worker about the key rotationCryptoRewrapBusProcessorhandles individuals key rotations (rewraps) of the key.The idea is that user post a request to Corda saying it wants to rotate a key. Rest Worker then publishes a message to Kafka (first new message) that key rotation is initiated. Crypto Worker picks up this message and finds out how many keys are required to rotate (rewrap with the new wrapping key) - this is done by
CryptoRekeyBusProcessor. For each of these keys it posts a message to Kafka with individual key request. This is a second new message. Messages are picked up byCryptoRewrapBusProcessorwhich then do the individual rewrap of the key.Design doc: Key rotation
API PR:1232