You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changing key state should respect key state model which is not working now. For example, it is possible to destroy private key (key item) and then use operation compromise (key) to set private key back to compromise state since that operation is applied without check on all items
check if key state change is valid when making it on key (key item), applied to all key items. Such an operation should be applied only to key items where it is valid state transition
same is valid for enable/disable operation on whole key. Now it throws exception if you try to enable key and one of key items is already enabled
check if key state change behave correctly also for bulk operations
consolidate messages in event history for changing key state: Key is already DESTROYED and Key is already destroyed. Label of KeyState enum can be used.
rename KeyState enum COMPROMISED_DESTROYED to DESTROYED_COMPROMISED (also label and code)
add check before cryptographic operations in CryptographicOperationService if key used is enabled and in state Active
The text was updated successfully, but these errors were encountered:
Changing key state should respect key state model which is not working now. For example, it is possible to destroy private key (key item) and then use operation compromise (key) to set private key back to compromise state since that operation is applied without check on all items
Key is already DESTROYED
andKey is already destroyed
. Label ofKeyState
enum can be used.KeyState
enumCOMPROMISED_DESTROYED
to DESTROYED_COMPROMISED (also label and code)CryptographicOperationService
if key used is enabled and in stateActive
The text was updated successfully, but these errors were encountered: