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/Issue | HTTP Response Code | Possible Cause and Fix |
|---|---|---|
Validation errors:\nprotection_policy_name: protection_policy_name is a required field | 422 Unprocessable Entity | This error will occur when the protection policy name is not specified in the request parameter of protect and reveal operations. To fix this error, provide the required field protection_policy_name in the payload. |
Validation errors:\ndata: data is a required field | 422 Unprocessable Entity | This error will occur when the data to be protected is not specified in the request parameter of protect operation. To fix this error, provide the required field data in the payload. |
Validation errors:\nprotected_data: protected_data is a required field | 422 Unprocessable Entity | This error will occur when the data to be revealed is not specified in the request parameter of reveal operation. To fix this error, provide the required field protected_data in the payload. |
Validation errors:\ndata_array: data_array is a required field | 422 Unprocessable Entity | This error will occur when the data to be protected is not specified in the request parameter of bulk protect operation. To fix this error, provide the required field data_array in the payload. |
Validation errors:\nprotected_data_array: protected_data_array is a required field | 422 Unprocessable Entity | This error will occur when the data to be revealed is not specified in the request parameter of bulk reveal operation. To fix this error, provide the required field protected_data_array in the payload. |
Input buffer is too short (len=0), it has to be at least 2 bytes long | 422 Unprocessable Entity | Dataset-related errors will occur when the data to be protected does not comply with the protection policy specifications. To fix this error, provide the data with minimum number of required characters. |
Input version header is invalid | - | This error occurs during the reveal operation when the version header is specified in the incorrect field (internal version is passed in the external version field and vice-versa) or the invalid version header is passed. |
The registration token cannot be used to register CRDP clients | 400 | These error will occur when incorrect registration token is used to register CRDP clients on the CipherTrust Manager. To fix this error, provide the correct registration token. |
token is missing required claim: exp claim is required | 401 | This error will occur when the exp claim is missing in the JWT.To fix this error, provide the required exp claim in the JWT. |
signing method is invalid | 401 | This error will occur when the JWT is using unsupported algorithm. To fix this error, use the supported algorithm RS256. |
token has invalid claims: token is missing required claim: iss claim is required | 401 | This error will occur when issuer is provided in the application configuration but missing in the JWT. To fix this error, provide the required iss claim in the JWT. |
