We've successfully set up an FTP connection with PGP encryption in our Celigo integration. Sending files to the FTP server (to our vendor) works perfectly. Files are encrypted correctly, and we can confirm that our vendor can decrypt the files properly.
However, we're running into an issue when importing files via FTP. Celigo throws the following error:
"The PGP signature could not be verified because the provided PGP Public Key does not match the Private Key that was used to sign the file. Please retry the request with the correct Public Key."
We’ve double-checked that the connection configuration includes the correct PGP public and private keys. These same keys work fine when decrypting the file manually using Kleopatra, so we’re confident they’re valid.
Has anyone encountered this before? Is there something specific Celigo expects in terms of how the file is signed or how the keys are formatted?
Sorry, if I’m stating the obvious here, but just in case this is helpful:
Typically, your company will have a “Private Key” and “Public Key”, AND your vendor will create their “Private Key” and “Public Key”.
For sake of clarity, we’ll give these explicit names:
your_private_key
your_public_key
vendor_private_key
vendor_public_key
When configuring the FTP connection in integrator.io, you’ll use your_private_key and vendor_public_key. Here’s a screenshot where I use the naming convention instead of actual keys:
I can confirm that what we're doing is exactly what you describe. We have a public key given to us by the vendor (the bank) that's what I entered in the PGP public key. I generated my own public/private key as well. I gave my public key to the bank and populate the PGP private key with my private key
