MuleSoft · SFTP Connector
SFTP Connector fails with a PPK identity file
SFTP Connector 2.0.0 and later cannot use a PPK identity file for public key authentication, because the Apache Mina library does not support that format. Convert the key to PEM with PuTTYgen and point the identity file setting at the PEM file.
VerifiedLast verified
01Error text
The Apache Mina library doesn't support the PPK file format, so the application fails.02Likely causes
- The connection uses the
PUBLIC_KEYpreferred authentication method with an identity file in PPK format. - The Apache Mina library used by SFTP Connector 2.0.0 and later does not support the PPK file format.
03How to fix it
- Open the PPK key in PuTTYgen and export it in PEM format.
- Set the identity file in the SFTP connection configuration to the PEM file.
- Redeploy and test the connection.
iNotes
The docs describe this as a failure and do not quote a fixed log message, so the text above is the docs' own description.
04Official documentation
→Related errors
- SFTP:INVALID_CREDENTIALSSFTP:INVALID_CREDENTIALS means authentication against the SFTP server failed because the credentials are invalid. Correct the user, password or key in the SFTP connection configuration.
- SFTP:KEY_EXCHANGE_FAILEDSFTP:KEY_EXCHANGE_FAILED means the app started an SSH connection to the server and failed at the key exchange step. Compare the algorithms the server requires with what the connector offers, using the server configuration and SSH trace logging.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer