Skip to content

ENT-14766- Sample to support the key rotation#122

Draft
filipesoliveira wants to merge 1 commit intorelease/4.12from
filipe.oliveira/ENT-14766
Draft

ENT-14766- Sample to support the key rotation#122
filipesoliveira wants to merge 1 commit intorelease/4.12from
filipe.oliveira/ENT-14766

Conversation

@filipesoliveira
Copy link
Copy Markdown

The bilateral agreement must be updated before performing a key rotation. This is because the parties are stored in the state and subsequently used in the flow. Once the key rotation occurs, these parties will contain outdated public keys, which will prevent the flow from executing, as it will no longer be able to establish a communication channel with any party that has rotated its key.

DO NOT MERGE THIS PR.

@filipesoliveira filipesoliveira changed the title ENT-14766- Sample to support the key rotation. ENT-14766- Sample to support the key rotation Mar 31, 2026
@filipesoliveira filipesoliveira marked this pull request as draft March 31, 2026 10:15
// Obtain a reference to a notary we wish to use.
/** Explicit selection of notary by CordaX500Name - argument can by coded in flows or parsed from config (Preferred)*/
final Party notary = getServiceHub().getNetworkMapCache().getNotary(CordaX500Name.parse("O=Notary,L=London,C=GB"));
final Party notary = getServiceHub().getNetworkMapCache().getNotary(CordaX500Name.parse("O=TestNotaryService, L=London, C=GB"));
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be ignore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant