Bug #8626
closed
Bug #8593: UserManagement need to have hashed password for both Linux and AIX
Adapt DirectiveEditor for master-slave password fields
Added by François ARMAND almost 8 years ago.
Updated over 7 years ago.
Category:
Web - Config management
Description
This subtask of #8593 is in charge of adapting all the UI logic to able to:
- have a master password field (for Linux hash variable) that send user input to a slave password field (for AIX hash variable),
- the password field must not have an actual HTML output
Files
- Subject changed from Adapt DirectiveEditor for master/slace password fields to Adapt DirectiveEditor for master-slave password fields
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1123
I think that that output is not the expected on: look at the attached text for the form
Hum, interesting. It is the "expected", because the value of the master password variable IS a linux hash. I will see how I could change the feedback to better explain. I could perhaps output the different values (linux, aix) ?
François ARMAND wrote:
Hum, interesting. It is the "expected", because the value of the master password variable IS a linux hash. I will see how I could change the feedback to better explain. I could perhaps output the different values (linux, aix) ?
actually, my main concern was the label below. But yes, you are right also
ha - I have a display problem when migrating from v6.0 to v7.0:
directives has two entries, first one doesn't show the current password hash, second one does
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.12 and 3.2.5 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by