Story

As a user of Cluster Log Forwarding,
I want to rely upon username and password to connect to my outputs that are managed by third parties
so that I do not depend upon certificates or mutual tls
 

Acceptance Criteria

• Username and passwords are not visible in the configuration as plain text
• Integration test that utilizes username and password for each output type that supports it (e.g. kafka, fluent, cloudwatch..)
• Username and password is not supported for OpenShift Logging managed Elasticsearch store

Notes

• Modify verification checks to require username and password as a set