Open upgradingdave opened 4 months ago
@upgradingdave I wasn't able to reproduce the issue with 8.5 - although in Operate you will see the backslash with an escape character (that's a limitation in JSON that those have to be escaped), in the connector itself, the backslash is unescaped and passed to AWS in its original format. Is it possible that the authentication issue was caused by something different?
On the other hand, I found that it's not possible to use unescaped backslashes inside connector secrets. Because of how the secret replacement currently works (we serialize variables to string and replace secret syntax in that string), substituting a value that contains an unescaped backslash results in invalid json, and the value cannot be deserialized again. As a workaround, such backslash characters need to be escaped in connector secrets.
FYI @sbuettner
Describe the Bug
An extra backslash character (
\
) is added to secrets when the secret value also contains a\+
character sequence.This is a problem because AWS will generate secrets and sometimes those secrets contain backslashes
\
. If an extra backslash is added, this breaks the authentication.Steps to Reproduce
123\+45
into theSecret Key
field of the Credentials Authentication Sectionauthentication
instance variable for the task has an extra backslash character added:\
.Expected Behavior
The secret value should be sent to AWS exactly how it's entered into Web Modeler. No extra backslashes should be added.
Environment