Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
-
Empty show more show less
Description
problems
- Session table is split in two tables (session / sessionInternalUniqId) which are synced in code. They should be combined
remove direct session access so that the authenticated user is kept just as user id in session→ DONE but must be rechecked- change session table to in memory table to improve performance. This should bed done with https://jira.translate5.net/browse/TRANSLATE-3574 in the next step. Reason is, each worker currently writes entry in the session which can easy lead to full table and memory limits. Until we refactor the workers, this will stay as it is.
- Check if really the whole userdata must be in the session, since only the userId is ncessary to load the user on Session Loading
Session handling got to complicated through the years and is probably responsible for a lot of not authenticated errors that we have via theRootCause.
Therefore it should be redone.
Attachments
Issue Links
- blocks
-
TRANSLATE-2217 List refactoring and code maintenance needs in translate5
- Selected for dev
- is blocked by
-
TRANSLATE-3574 Session table as memory table
- Open
- is duplicated by
-
TRANSLATE-3507 Refactor Session handling
- Done