Troubleshooting Data Security issues
Follow these troubleshooting tips to address common Data Security-related issues. If you require further assistance, please reach out to our team for support.
PGP Errors
| Error Message | Cause | Solution |
|---|---|---|
| Sender Decryption: “openpgp: incorrect key” |
Encrypted file uploaded was encrypted using the wrong Sender key | Encrypt the file with the correct Sender key, which can be viewed in CFT Portal |
| Sender Decryption: “invalid data: tag byte does not have MSB set” |
File uploaded was not encrypted File uploaded was encrypted but was corrupted • File contents were modified • File contents were truncated |
Encrypt the file with the correct Sender key before uploading |
| Sender Decryption: “openpgp: unsupported feature: message is not integrity protected” |
• Manually disabled MDC in their PGP tool during encryption • Used outdated encryption algorithm without MDC support • Used an outdated PGP tool version with the option to disable MDC |
• Encrypt the file with MDC enabled • Ensure supported MDC algorithms are used Refer to the PGP section for more information |
| Receiver Encryption: “cannot encrypt a message to key id because it has no valid encryption keys” |
Receiver key does not have valid encryption keys It could be due to expired key Could be due to key not having the required self signature |
Need further investigation on how the key was generated |
| Receiver Encryption: “error in reading key ring: …” |
Invalid receiver key string | Verify that the receiver key is valid Upload the receiver key again |
| Sender Decryption: “openpgp: invalid data: parsing error” or “unexpected EOF” or “openpgp: invalid data: armor invalid” or “illegal base64 data at input byte 0” |
File uploaded was encrypted but was corrupted • File contents were modified • File contents were truncated |
• Verify if your file was modified or truncated before it was uploaded • Verify if the file CFT received was truncated, due to network issues: • GET File Details API: If one of your applications is an HTTP client, you can use our GET File Details API to verify the content length (in bytes) of the uploaded file • SFTP Job Logs: If your file was uploaded using scheduled/manual SFTP job run, you can view the logs on our CFT Admin Portal to determine the number of bytes uploaded for your file • If the file content lengths are different, please upload your file again |
| Sender Decryption or Receiver Encryption: “get object failed: operation error S3: GetObject, https response error StatusCode: 412 … api error PreconditionFailed: At least one of the pre-conditions you specified did not hold …” |
• A new file with the same name but different content was uploaded shortly after this file • The original file was overwritten, so CFT could not retrieve it from S3 |
• This file will not be processed because it has been overwritten • The most recent file will be processed successfully • To avoid this error in the future, ensure that file names are unique to prevent overwriting existing files. You may use these CFT features to assist you: → HTTP uploads: Add the header x-cft-do-not-overwrite: true in your upload request → SFTP uploads: Enable the SFTP Unique Files option in your workflow using the CFT Admin Portal |
SLIFT Errors
| Error Message | Cause | Solution |
|---|---|---|
| Sender Decryption: “Certificate does not match any valid recipient” |
Encrypted file uploaded was encrypted using the wrong Sender key | Encrypt the file with the correct Sender key, which can be viewed in CFT Portal |
| Sender Decryption: “First field should be an Object Identifier” or “Initialisation Exception -> Invalid ContentInfo, number of fields=0” |
File uploaded was not encrypted | Encrypt the file with the correct Sender key before uploading |
| Sender Decryption: “java.lang.NullPointerException” |
Before encrypting the file, the public key conversion from .crt to .cer was invalid | Refer to the SLIFT section for the steps on converting .crt to .cer using OpenSSL |
| Receiver Encryption: “No supported data to decode. Input type: PEM” |
Invalid receiver key string | Verify that receiver key is valid Upload the receiver key again |
| Sender Decryption or Receiver Encryption: “get object failed: operation error S3: GetObject, https response error StatusCode: 412 … api error PreconditionFailed: At least one of the pre-conditions you specified did not hold …” |
• A new file with the same name but different content was uploaded shortly after this file • The original file was overwritten, so CFT could not retrieve it from S3 |
• This file will not be processed because it has been overwritten • The most recent file will be processed successfully • To avoid this error in the future, ensure that file names are unique to prevent overwriting existing files. You may use these CFT features to assist you: → HTTP uploads: Add the header x-cft-do-not-overwrite: true in your upload request → SFTP uploads: Enable the SFTP Unique Files option in your workflow using the CFT Admin Portal |
Signature Verification Errors
| Error Message | Cause | Solution |
|---|---|---|
| Signature Verification: “No matching signature” |
The file uploaded was not signed or signed using the wrong Signature Verification Key | Sign the file with the correct Signature Verification key |
| Key creation: “Could not submit create request” |
The key entered is not in Armored or Binary format | Enter the key in the correct format |
