User story #3282
closed
Add a password input field in Directive
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).
Updated by Jonathan CLARKE almost 12 years ago
Sounds great. One detail: if a password is already defined, it should be displayed above the field to change the password, and extra text should be added in front of that saying "Change password:".
Updated by François ARMAND almost 12 years ago
It seems more convenient to be able to see the password (you are not really likelly to use Rudder in a given cyber café...).
Updated by François ARMAND almost 12 years ago
Evolution:
- we want to use the "INPUT" XML field in technique for password, with two new constrains;
- a new type: password;
- a new constrain: passwordHash. That constrain accept a list of hashes, with the following meaning:
- a list on zero hashes means "show all defaults hashes"
- a list of one hashes is a "no choice" for the user
- a list of several hashes display a select, in the order given in the list
- to make the user interface clearer, we want to have three select boxes to update the password :
- 1/ Keep current password
- 2/ None
- 3/ [input] hash with: [select] <- a focus on these fields auto-change the radio to 3
Updated by Nicolas CHARLES over 11 years ago
- Status changed from 12 to Pending release
Updated by Matthieu CERDA over 11 years ago
Now, we have to update the existing promises to use this.
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Pending release to Released
This ticket has been addressed in version 2.6.0~beta1 of Rudder, which has just been released. Please see the changelog here: https://www.rudder-project.org/foswiki/System/Documentation:ChangeLog26.