A 3rd party requires that you encrypt the file you are sending to their SFTP.
If you would like to use your Public PGP Key in your VGS vault, please follow the steps below.
1. Base64 encode the Public PGP Key. Can use the terminal, command line, or online tools to do this for you. Please keep the header -----BEGIN PGP PUBLIC KEY BLOCK-----, the footer -----END PGP PUBLIC KEY BLOCK-----, and the line returns (see image below).
NOTE: don't use online tools for Private PGP Keys, please have your engineering team base64 encode your private key internally. If it is a Public PGP Key, then online tools are okay since this key is publicly available.
2. Create the VGS alias by either sending the base64 string from the previous step to your VGS HTTP Proxy (INBOUND or OUTBOUND routes), or to your VGS Vault API.
- Create an alias with the HTTP Proxy (link to INBOUND/OUTBOUND videos below).
- Create an alias with the Vault API (link below).
3. Please provide the VGS alias provided from the previous step to our VGS support team. Send an email to email@example.com to complete the operation setup for using the Public PGP Key in encrypting the file after revealing the aliases within your VGS SFTP Proxy.
In addition, you'll want to specify the Tenant ID, Route ID, and Filter ID that you would like to apply the public key after for your VGS SFTP Proxy. For example, the encryption should be done on Tenant ID tntabcd1234 for the SFTP Route ID 767a4639-a9a5-44aa-8170-b10bb086b791 after revealing the sensitive information via the Filter ID 859f95a1-6471-44f7-bae0-c35fcda5e34a.
4. Test the filter to make sure it works as expected (if possible). You should be able to decrypt the file if you hold the private key, or at least verify that the file is encrypted for the 3rd party.