Applies to Product- Power Automate
What’s happening?
The issue involves a file that has been encrypted as a .gpg file using a public key, which does not remain encrypted after being sent to the recipient using the SFTP connector in Power Automate. The file appears unencrypted on the recipient's side.
Reason:
The SFTP connector in Power Automate might be automatically decrypting the file upon transfer. There may be incorrect configuration or setup within the SFTP connector that does not preserve the file's encrypted state. Additionally, the receiving end may have an automated process that decrypts .gpg files upon receipt.
Resolution:
- Verify the integrity and successful encryption of the .gpg file prior to transferring it via the SFTP connector.
- Confirm if the correct public key corresponding to the recipient's private key was used during the encryption process.
- Check if the SFTP Connector in Power Automate is configured to handle .gpg files without altering the file format or content.
- Investigate if there is an intermediary process within the Power Automate flow that might be decrypting the file before it's sent.
- Review any settings or configurations on the recipient's SFTP server that might be automatically decrypting the .gpg files upon arrival.
- Consider redesigning the flow to ensure that the file remains encrypted during the transfer process, as the current method may not support the encryption type used.