Key Errors
This section lists the key related errors which could occur while using the CipherTrust Manager interfaces: Web, NAE, KMIP, CLI, and API.
Action | Error Information | Possible Cause | Remediation |
---|---|---|---|
Create Key | Invalid password for pkcs12, it should be base64 encoded | The password is not base64 encoded. | Encode the password in base64 format and retry. |
Use Key | Failed to locate the public key | Possible reasons: • User does not have permission to read the key. • Key has already been deleted. |
Ensure that the key exists and user has read access on the key. |
Delete Key | Key is not deletable | User does not have permission to delete the key. | Check the key properties and ensure that the user has required permissions on the key. |
• Read Key • Use Key |
Key usage mask (<VALUE> ) is not compatible with actual usage mask |
Key is being used for the crypto operation which it is not created for. | Refer to the CCKM API Guide for details and examples of key operations. |
• Create Key • Find Keys • Find Key • Versions • Read Key • Destroy Key • Update Key |
Error updating fingerprint in list of keys | Key is in state Destroyed or Destroyed Compromised state. | Validate the state of the key. |
Same as above | Failed to decode key material | Possible reasons: • key material could be malformed. • key material is not in hex. |
Contact Thales Customer Support, and provide them a copy of Syslog for analysis. |
Same as above | Invalid Key Material | Key data is either invalid or corrupted. | Contact Thales Customer Support, and provide them a copy of Syslog for analysis. |
Same as above | Cannot export key in |
Key is in state Destroyed or Destroyed Compromised state. | Validate the state of the key. |
Read Key | read on target is not authorized: verdict was deny: ReadKey | User is not authorized to perform read key operation. | Ensure that the user has appropriate rights and permissions. |