Actions
Bug #24755
closedBug #24017: Webapp can fail to start with null sessionid error
In case a NULL was introduced earlier in sessionid, login is impossible
Status:
Resolved
Priority:
N/A
Assignee:
Category:
Architecture - Code maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Parent corrects the fact that we introduce new null values for sessionId. But we can still have previously introduced one, and when we try to log, we get:
We don't want to make connection impossible because of an error in the past.
Files
Updated by François ARMAND 7 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5617
Updated by Clark ANDRIANASOLO 7 months ago
- Is duplicate of Bug #24757: Unable to log in - Server error added
Updated by François ARMAND 7 months ago
- Status changed from Pending technical review to Resolved
Closing as duplicate.
Actions