The key pool profiles are defined to generate number of keys that are prepared for the signing operation by the user. Once there is a signing request, the CSC component will use available key from the pool to sign.
However, when there is a change in the key pool, for example prefix of the keys is changed, or key pool is removed, the generated keys will not be removed from the database and they are indefinitely present.
They can be only removed manually from the database.
For better management of key pools, it would be good to implement endpoint for the key pool management, or key management in general. In such case, the CSC component will have a higher control on the defined key pools and configuration that can be eventually implemented in the UI.
The key pool profiles are defined to generate number of keys that are prepared for the signing operation by the user. Once there is a signing request, the CSC component will use available key from the pool to sign.
However, when there is a change in the key pool, for example
prefixof the keys is changed, or key pool is removed, the generated keys will not be removed from the database and they are indefinitely present.They can be only removed manually from the database.
For better management of key pools, it would be good to implement endpoint for the key pool management, or key management in general. In such case, the CSC component will have a higher control on the defined key pools and configuration that can be eventually implemented in the UI.