Actions
Bug #25444
closed
User password change no longer needs restart in doc
Pull Request:
Severity:
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Current doc states that change of password for security reasons requires a restart of Rudder :
After a configuration change on a user that might have a security impact (e.g., password reset if it may have leaked or permissions restriction), currently existing sessions will not be affected, so you need to restart the web application to enforce it (systemctl restart rudder-jetty).
This is no longer the case since #25407
Updated by Clark ANDRIANASOLO about 1 month ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO about 1 month ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder-doc/pull/1049
Updated by Clark ANDRIANASOLO about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-doc|84f6f7529731ebb11c6702d388cfe2e51892d95b.
Updated by Vincent MEMBRÉ about 1 month ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 17 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.7 which was released today.
Actions