User sensitive info is not protected properly

Passwords or any other security information that can be imported in context via CLI are showing in mistral log and mistral dashboard too.

Fix proposed to branch: master
Review: https://review.openstack.org/139936

Renat said on the comment:
>>>
Honestly, what mask_password() method does doesn't seem 1) obvious because there's no clear documentation on it 2) reliable enough for all situations we may have. I also would like to see some testing for that (I think it's possible to do if we apply some mocking testing etc.)
Generally, I would suggest that we create a special utility class Password with string representation like "****". And whenever we need to get a real value we will call a method get_value() or something like that.
Thoughts?
>>>

The other use case for passwords is passing them as parameters via environment __env, or workflow parameters.
We may also want to mask them in the DB: else the task context will be inspected and passwords exposed via API.

Change abandoned by Renat Akhmerov (<email address hidden>) on branch: master
Review: https://review.openstack.org/139936
Reason: Obsolete and almost impossible to rebase.

Fix proposed to branch: master
Review: https://review.openstack.org/207348

Here's my strong opinion about this ticket and some ideas of how we could address it.

* Any solutions based on guessing (any kinds of patterns etc.) what is secure information and what's not won't work out. Just because it's security and this is not a secure approach by definition.

Below are my ideas of how we could address it.

Client-side

An example of input data that we provide to Mistral in JSON format:
{
    "secure_key^&": {
 "key1": { "_secured": 1 },
 "key2": 2,
 "key3: 3
    }
}

So whenever we need to make something secure we just wrap a corresponding value with {"_secure": value} (we can use a different marker if needed). So the client knows that it needs to be passed to the server as a secure piece of information.

Server-side:

* We create a special data type (class SecuredData or Password) that has a string representation "*****"
* JSON SQLAlchemy type must account for this class and encode/decode info behind this class instances so that we don't keep passwords and other secure things in their original form in DB
* Every time we request a info via API we give only its string representation which is "*****"
* Every time in the server when we need to get a real value (to pass it to executor etc.) we extract a real value (i.e. using get_value() method)

Change abandoned by Lingxian Kong (<email address hidden>) on branch: master
Review: https://review.openstack.org/207348
Reason: Should find a generic way to fix the security problem, need more discussion with mistral team.

We can work with the ossp (openstack security project) to get a ossn security note, such as https://wiki.openstack.org/wiki/OSSN/OSSN-0052

this is the nova attempt at fixing a similar issue: https://review.openstack.org/#/c/220622

Heat's patch for the same issue (at debug level): https://bugs.launchpad.net/heat/+bug/1664792