You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Behavior:
In some older version parameters which represented passwords (e.g. DBMSPassword) the input field hid the value (e.g. pw is shown as: ********).
Additionally, in older version if a parameter was a PrivateKey (e.g. VMPrivateKey) the input field didn't mess up the PrivateKey from a string perspective (e.g. the private key is broken and can't be used by some artefacts such as the SSH service for virtual machines)
Expected Behavior:
Password parameter values are hidden, PrivateKeys are still valid after pasting them into the field.
Steps to Reproduce:
Use any CSAR (e.g. MyTinyTodo with MySQL) which has atleast one Password Parameter
Use any CSAR which has a PrivateKey Input Parameter
Other Information:
Params not beeing hidden or well formatted:
Some logs when the private key is really needed:
P.S.: I know we can just escape the returns, but well, does it have to be done?! :P
System Information:
Mac OS X with Docker Setup and Chrome
The text was updated successfully, but these errors were encountered:
miwurster
changed the title
[BUG] Input parameters of Passwords and PrivateKeys
Input parameters of passwords and private keys are visible in the UI
Jan 22, 2019
Current Behavior:
In some older version parameters which represented passwords (e.g. DBMSPassword) the input field hid the value (e.g. pw is shown as: ********).
Additionally, in older version if a parameter was a PrivateKey (e.g. VMPrivateKey) the input field didn't mess up the PrivateKey from a string perspective (e.g. the private key is broken and can't be used by some artefacts such as the SSH service for virtual machines)
Expected Behavior:
Password parameter values are hidden, PrivateKeys are still valid after pasting them into the field.
Steps to Reproduce:
Other Information:
Params not beeing hidden or well formatted:
Some logs when the private key is really needed:
P.S.: I know we can just escape the returns, but well, does it have to be done?! :P
System Information:
Mac OS X with Docker Setup and Chrome
The text was updated successfully, but these errors were encountered: