I’ve handled something like this before by manually (one time) encrypting the values using an Encrypt Field snap using a Passphrase-based Account. Then hardcoded those encrypted values in a mapper like you mentioned, with a Decrypt Field snap after it using the same Passphrase-based Account, to decrypt the values and use them at runtime.
Thanks Chris. That is really useful. I will try this option, but I am guessing that the decrypted value is still available to the developers (much smaller population which is definitely better than before). I was wondering if there is an option like storing the credentials in an account, where it is not possible for anyone to look at these.
If anyone thinks that there are other mechanisms I am missing, please do let me know.
