During the signing operation, we take the first usable key.
However, there can be a situation that the key was deleted from the signing engine and although CSC component will take the keys from its database, it won't be able to use it and receive an error.
In such case, it is useful to implement retry mechanism that should take another key and try signing with different key. The retry count can be configured in the application properties.
The CSC will respond with error when the signature cannot be created after number of defined retries.
Obviously, this should behave differently for different signature types:
- one time will not use retry, it should be bind to specific credential
- session will need to use the same key, retry can be applied only for the first signature in session
- one-time will use retry mechanism
During the signing operation, we take the first usable key.
However, there can be a situation that the key was deleted from the signing engine and although CSC component will take the keys from its database, it won't be able to use it and receive an error.
In such case, it is useful to implement retry mechanism that should take another key and try signing with different key. The retry count can be configured in the application properties.
The CSC will respond with error when the signature cannot be created after number of defined retries.
Obviously, this should behave differently for different signature types: