The current signature enables worst practices for password storage.
While I understand that the UsernamePassword provider is not recommended, if it is being used, then requiring a SecureString will force developers to "secure" the password before calling the SDK.
The current signature enables worst practices for password storage.
While I understand that the UsernamePassword provider is not recommended, if it is being used, then requiring a SecureString will force developers to "secure" the password before calling the SDK.