Best Practice SecureString in plain string credential property fields

[lukasziebold]

Hi @Kristopher,

would you mind taking another look at my follow-up questions?

@lukasziebold

Now, am I missing something? Is this password variable accessible somewhere else? Why am I still getting the SecureString Misusage flag? Is there a better workaround to deal with plain string credential property fields? What about that idea of making credential property fields require a SecureString?

You might also want to address @cclements concerns:

'Send SMTP Mail Message' Password - SecureString

What’s odd is that they seem to be concerned with the improper use of the SecureString and yet have activities that accept passwords as plain text, such as the Send Exchange Message. If you are getting your credentials from an asset, you are forced to cast it to string to use these activities. This will trigger the analyzer error. Solo developers can just disable this rule. But what if you are enforcing a governance policy at the enterprise level?

Thank you
Cheers