Soap Execute snap - Account creds in header
I’m building a custom SOAP Execute snap to replace Netsuite snaps to work around a limitation with custom fields in Netsuite snaps that require fields entered to not be null.
I’ve modeled my SOAP e...
Forum Discussion
I worked with Snaplogic support to solve this, shout out to Mina!
I basically just set up a simple AES encryption passport as an account, encrypted a file and saved it to the specific project to limit permissions, and set up the pipeline to join in the password so everything stays in memory only.
Unfortunately this still logs the password with the SOAP request, but we consider this a good enough solution that avoids storing the password directly in the definition of the pipeline! If anyone has a tip on how to obfuscate the password in the logs that’d be rad to hear but for now this problem is effectively solved.
