Actions
Bug #25322
closedSession could be null when checking user status
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
It bothers me each time
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
117
Name check:
To do
Fix check:
Checked
Regression:
No
Description
There was an unhandled case in the parent issue : a NullPointerException happening because session cannot be invalidated
Also when session is invalidated, no one know that it has actually been and because of which action on the user
Updated by Clark ANDRIANASOLO 4 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 4 months 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/pull/5822
Updated by Clark ANDRIANASOLO 4 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|ba4556fb2c5ee12df0d03be78b7d7572036e5f7e.
Updated by Vincent MEMBRÉ 3 months ago
- Status changed from Pending release to Released
- Priority changed from 118 to 117
This bug has been fixed in Rudder 8.1.7 which was released today.
Actions