Actions
Bug #2821
closed
Rudder upgrade broken in case of hashed LDAP password in slapd.conf
Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Rudder upgrade broken in case of hashed LDAP password in slapd.conf, if the slapd.conf rootpw is hashed, the rudder upgrade script tries to use this hashed value to connect and fails.
We should either assume the password to be "secret" in that case (worst option) or ask the user (best one).
Updated by Nicolas PERRON over 12 years ago
- Status changed from New to In progress
The problem comes from the choice of the file for having LDAP credentials. We use forst slapd.conf and then rudder-web.properties. The order should be inverted.
Updated by Nicolas PERRON over 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:03e8d4616c7793d235fb20a852ae4b1e9ccee4a8.
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions