Actions
Architecture #24729
closedAllow using a different password hash algorithm for each local user
Fix check:
To do
Regression:
No
Description
We should be able to derive the hash from the password value, so no need for a global fixed value. Future hash will use a shadow-like format containing the chosen algorithm.
Updated by Alexis Mousset 8 months ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset 8 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5604
Updated by Clark ANDRIANASOLO 7 months ago
- Assignee changed from François ARMAND to Alexis Mousset
Updated by Alexis Mousset 7 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|298ed68d1dd591255892ed09993eb8ddce88bd51.
Updated by Alexis Mousset 5 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~alpha1 which was released today.
Updated by Clark ANDRIANASOLO 5 months ago
- Related to Bug #25293: API documentation for user management in 8.2 added
Updated by Clark ANDRIANASOLO 4 months ago
- Related to deleted (Bug #25293: API documentation for user management in 8.2)
Actions