Affects Version/s: 5.0.15
Fix Version/s: 5.0.16
Currently, the PasswordField component does not display it's value. Although this indeed represents best practices in handling passwords (e.g. if the password field did display its value although masked, it would still be visible in the source), the current behavior stumps new users and unnecessarily enforces a particular process (e.g. never display the password) or forces a user to split page containing the password field (e.g. what would have other in orderwise been a single page to create and update a value, now has to be two different pages) to avoid validation issues.
The requested parameter (e.g. "displayValue") would contain a warning in bold that displaying the password value could be a security issue (and potentially log a warning). The default value of the parameter should be "false", that is it wouldn't display the password, unless explicitly enabled.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|58d 8h 54m||1||Howard M. Lewis Ship||31/Oct/08 18:28|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||5.0.16 [ 12313427 ]|
|Resolution||Fixed [ 1 ]|
|Summary||Add a parameter to PasswordField component to populate the password value||PasswordField should not update its value parameter when the submitted value is blank|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Issue Type||Bug [ 1 ]||Improvement [ 4 ]|
|Affects Version/s||5.0.15 [ 12313429 ]|
|Field||Original Value||New Value|
|Fix Version/s||5.0.16 [ 12313417 ]|
|Fix Version/s||5.0.15 [ 12313350 ]|