Closed paullatzelsperger closed 2 months ago
Aligns the "active-key" operation with the decision record
Briefly state why the change was necessary.
KeyPairActivated
DidDocumentService
keyContext
KeyPairResource
"JsonWebKey2020"
KeyPairStates#ACTIVE
KeyPairStates#ACTIVATED
PArticipantContextEventCoordinator
"inactive"
KeyPairService
active
activateKey
KeyPairAdded
Closes # <-- insert Issue number if one exists
_Please be sure to take a look at the contributing guidelines and our etiquette for pull requests._
What this PR changes/adds
Aligns the "active-key" operation with the decision record
Why it does that
Briefly state why the change was necessary.
Further notes
KeyPairActivated
event (and associated methods), which is consumed by theDidDocumentService
keyContext
field to theKeyPairResource
(and the associated DB schema) to track the "context" of the key, e.g."JsonWebKey2020"
KeyPairStates#ACTIVE
toKeyPairStates#ACTIVATED
for consistencyPArticipantContextEventCoordinator
emits a warning log if a participant is added and activated, but its only key is in the"inactive"
stateKeyPairService
: when a key is added in theactive
state, theactivateKey
method is invoked in the same transactionDidDocumentService
reacts to theKeyPairActivated
event instead ofKeyPairAdded
Linked Issue(s)
Closes # <-- insert Issue number if one exists
_Please be sure to take a look at the contributing guidelines and our etiquette for pull requests._