Actions
Bug #24755
closed
Bug #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 
Updated by
Actions