Hi. I got it to work sending both from a local IS to my WMIO tenant and from another service on the same tenant over HTTP, so it should work equally well from another WMIO tenant.
When you define the PGP connector account, you upload your .asc public and private key files. So, there is no need to send them as inputs separately.
When you encrypt, it’s best to loadAs bytes.
When you send in the input data to decrypt, only send in encrypted message, not the PGP headers and trailers. Then, if sending over HTTP base64 encode the bytes - set use new line to false. Use variable substitution to send the data in the body of the POST. For example, {“encryptedString”:“%encryptedString%”}
The tutorial here uses the raw bytes and streams to and from Azure blob storage:
webMethods.io Integration PGP encryption & decryption - Knowledge base - Software AG Tech Community & Forums
It’s not obvious, because loadAs defaults to bytes.
Hope this helps,
Theo
