Actions
User story #3282
closedAdd a password input field in Directive
Status:
Released
Priority:
3
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We need a kind of password field for Technique parameters, that will be translated visually as follow in a Directive:
- a password type input text (with *** in place of characters)
- a list of hash algorythme to use (crypt, md5, sha256, etc)
- if the password field was already filled, the resulting hash, for ex: SHA1:40285A0854205
In LDAP, we only store the hashed value (with the algo used).
The field is considered:
- empty if no value if filled in the input field, nor no hash already exists;
- not updated if no value is filled in the input field and a hash already exists;
- updated as soon as a value is filled in the input field.
That means that a password can never be blanked (and so, if the Technique logic require that possibility, a second field "use password / blank password" should be created).
Actions