Troubleshooting
This section describes the issues you may run into and how to resolve them. If you face an issue that is not listed here, contact Thales Customer Support.
| Error Message | Possible cause |
|---|---|
keyManagerHost and registrationToken are the mandatory parameters for client registration. | Occurs when keyManagerHost or registrationToken are not passed in the register client API call. |
Provided KeyManager host is invalid. Provide a valid KeyManager host. | Occurs when invalid keyManagerHost is passed in the register client API call. |
Unable to fetch client configuration from Key Manager after client registration. | Occurs when client configuration can't be fetched from the key manager. |
Protection Policy name cannot be null or empty. | Occurs when protection policy is not passed in the protect, reveal, or reprotect call. |
Could not get protectionPolicyName. | Occurs when protection policy doesn't exist on the key manager. |
Cannot get key for local encryption. | Occurs when key used for local encryption doesn't exist on the key manager. |
Cannot perform crypto operation under Pre-Active state. | Occurs when crypto operations are performed using pre-active keys. |
Input data length is invalid. Luhn requires minimum 3 digits. | Occurs when cryptographic operations are performed on luhn compliant data less than 3 digits. |
Luhn validation fails for input data. | Occurs when data is not luhn compliant. |
Protection Policy version can not be more than 999. | Occurs when protection policy version exceeds the maximum permissible limit that is 999. |
Error while protecting the data: Version information is invalid. | Occurs when incorrect version header is passed in the API calls. |
Version is invalid. | Occurs when invalid version is padded in the reveal API call. |
clientmanagement.ClientManagementUtility, encoding is not supported. | Occurs when encoding is not supported. |
| Problem | Description |
|---|---|
| Key won’t exported to the cache | — Check the key’s exportable setting. Only exportable keys can be downloaded to the symmetric key and persistent key caches. — Check the port configuration. The keys can only be exported only if the port allows download of exported keys |
| Can’t create keys when server connection is disrupted. | This works as designed. The persistent key cache is not used for creating keys. The client can only create keys on the Key Manager. |
| Need to debug using log file | You have the option to re-set the Log_Level parameter setting in the CADP_for_JAVA.properties file to HIGH or DEBUG to obtain more log file entries. You can use the method writeToLog() to write messages directly to the log file. |
