Actions
Bug #27379
closed
Users cleanup configuration is still too strict for disabling/deleting
Bug #27379:
Users cleanup configuration is still too strict for disabling/deleting
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
In #25479 we already lifted a bit the duration with the duration for user getting disabled/deleted, but we still have a lot of user for who "rudder just work" who has the bad surprise to not be able to connect after a busy period doing anything but Rudder.
So we will set the values to:
- 180 days before disabled,
- never (or > 5 years if "never" does not exist) for user deletion.
Updated by François ARMAND 7 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 7 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/6547
Updated by Anonymous 7 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|c1c02eff9a1f1b75a405b764faa4d95cfd1488d6.
Updated by Clark ANDRIANASOLO 6 months ago
· Edited
The default duration on startup could be fixed for this :
2025-09-04 11:32:36-0400 INFO application - Key 'rudder.users.cleanup.account.disableAfterLastLogin' is absent, defaulting to: PT4320H 2025-09-04 11:32:36-0400 INFO application - Key 'rudder.users.cleanup.account.deleteAfterLastLogin' is absent, defaulting to: PT2562047H47M16.854775807S
Updated by Clark ANDRIANASOLO 6 months ago
- Subtask #27522 added
Updated by Clark ANDRIANASOLO 6 months ago
- Fix check changed from To do to Checked
There is a new configuration sample, and the default is working, but the logs can be improved : #27379
Updated by Vincent MEMBRÉ 6 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.3.4 which was released today.
Actions