Troubleshooting
Tokenization API Call Failure Error Messages and Workarounds
Following error messages may occur when an Tokenization API call is made:
| Message | Description |
|---|---|
| --tlsv1.2: is unknown. | Only CURL version 7.34 or later supports the --tlsv1.2 option. If you get this error message, upgrade to CURL version 7.34 or higher. |
| API call aborted and no JSON vector elements are processed. | These are error messages which pertain to the whole JSON vector. In other words, in these cases no vector elements are processed at all. The whole operation is aborted. |
| User name and/or password mismatch. | Due to a wrong user name and/or password, access to the CipherTrust Vaultless Tokenization Server is denied. |
| Unknown JSON keyword encountered. The valid keyword for the log request is loglevel. | For the REST API called log, the only valid keyword on the left of the JSON valuename-value tuple is loglevel. |
| Could not parse JSON input, perhaps it is too long. | An input size of 1 MByte cannot be exceeded. It could also mean that the JSON input is malformed. |
| User name and/or password missing. | Either the user name, or the password, or both are missing from the request. |
| This user does not have permission to tokenize. | While the user exists and the password is correct, this particular user does not have the permission to tokenize. Consider assigning this user the permission to tokenize via the GUI. |
| User name found, but the user is not marked active. | While the user exists and the password is correct, this particular user is not marked as an active user. Consider marking this user an active user in the GUI. |
Invalid operation. Use/vts/rest/v2.0/tokenize, or/vts/rest/v2.0/detokenize. | An invalid URL was specified. Allowed operations are:/vts/rest/v2.0/tokenize,/vts/rest/v2.0/detokenize, or/vts/rest/v2.0/log. |
| No password specified. | While a user name was specified, the password is missing. |
| User name not found. | The specified user name exists neither in the local database which is configured via the GUI, nor in the optional LDAP database. |
| LDAP user found in local database, but LDAP is disabled. | Presumably due to a prior use of LDAP, an LDAP user was cached in the local database, but LDAP has since been disabled, disallowing authentication with this user. Prior to using LDAP users for authentication, at least one of the groups this user belongs to according to the LDAP database must be configured as a user group via the GUI. |
| API call aborted, one JSON vector element fails, others are processed. | These messages pertain to only one element of the JSON vector. In these cases, one vector element may result in an error, but all other vector elements are still processed. |
| The length of the token exceeds 128 Kbytes. | The length of a token is limited to 128 KiB. However, the token supplied was longer than 128 KiB. |
| Unknown JSON keyword encountered. Valid keywords for the detokenize request are tokengroup, token, and tokentemplate. | For the detokenize operation, only three specific keywords are allowed on the left side of a JSON tuple: tokengroup, token, and tokentemplate. Please review and correct your JSON string. |
| The length of the data exceeds 128 Kbytes. | The length of the input data is limited to 128 KiB. However, the input data supplied was longer than 128 KiB. |
| Unknown JSON keyword encountered. Valid keywords for the tokenize request are tokengroup, data and tokentemplate. | For the tokenize operation, only three specific keywords are allowed on the left side of a JSON tuple: • tokengroup • data • tokentemplate |
| Please review and correct your JSON string. | A token group was specified in the JSON input, but it doesn't exist in the GUI-administered configuration database. Consider adding this token group via the GUI. |
| The requested key name was not found on the CipherTrust Key Manager. | A key name was configured via the GUI and now used in an operation, however this key name does not exist on the CipherTrust Key Manager. |
| The token group specified was not found in the database. | The token group was not found on CT-VL. |
| tokengroup not specified in JSON request. | The JSON tuple named tokengroup is missing from a JSON vector element. A tokengroup must be specified. |
| The requested combination of tokentemplate and tokengroup was not found in the tokentemplate table. | Either the tokengroup specified has not been entered via the GUI, or the tokentemplate has not been entered via the GUI, or the token template of the same name has been entered, but for a different tokengroup. Please ensure that the tokentemplate you are trying to use has been entered for the tokengroup you are trying to use. |
| It is not allowed to specify the FPE-luhn token format with a non-zero keepright value. | After accounting for keepleft and keepright, not enough input characters are left to successfully tokenize the input. When you use the FPE token format, the number of input characters must exceed the sum of the Keep Left value and the Keep Right value by at least two. When you use the FPE-luhn token format, the number of input characters must exceed the sum of the Keep Left value and the Keep Right value by at least three. |
| There are not enough input characters for the detokenize operation. | At least two input characters are needed in the token in order to try to detokenize it. |
| Token format FPE-luhn is only compatible with an alphabet consisting of the 10 decimal digits (in ASCII encoding). | The FPE-luhn token format cannot be used with an alphabet containing letters and/or special characters. It must be used with an alphabet only containing the 10 digits. |
| After accounting for the keepleft and keepright requirements, not enough input characters left to tokenize. | When you use the FPE token format, the number of input characters must exceed the sum of the keepleft value and the keepright value by at least two. |
| Luhn check failed for input data. | The token format FPE-luhn was specified, but the input data sports an incorrect Luhn checksum. Please check your input data, or change the token format from FPE-luhn to FPE. |
| After accounting for keepleft and keepright, there are not enough input characters present to successfully tokenize. | • When you use the FPE token format, the number of input characters must exceed the sum of the keepleft value and the keepright value by at least two. • When you use the FPE-luhn token format, the number of input characters must exceed the sum of the keepleft value and the keepright value by at least three. |
| Token does not begin with the prefix specified in the database. | While a certain token prefix is specified in the token template which is being used in the JSON input, the token seen in the JSON input does not sport this particular token prefix. |
| The specified token only contains the prefix and no payload. | While the token seen in the JSON input sports the correct token prefix, there are no other characters present in the token. |
| Luhn check failed for input token. | The token format FPE-luhn was specified, but the token specified sports an incorrect Luhn checksum. Please check your input data. |
| There are not enough input characters present to successfully detokenize. | • When you use the FPE token format, the number of input characters, not counting the token prefix, must exceed the sum of the keepleft value and the keepright value by at least two. • When you use the FPE-luhn token format, the the number of input characters, not counting the token prefix, must exceed the sum of the keepleft value and the keepright value by at least three. |
