[MAGNOLIA-7028] MgnlUser bean consistency Created: 16/May/17  Updated: 26/Mar/19  Resolved: 15/Jun/17

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 5.5.5

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: performance
Remaining Estimate: 0d
Time Spent: 2d 3h
Original Estimate: Not Specified

Issue Links:
Relates
relation
is related to TASKMGMT-28 Avoid creating User throwaway objects... Accepted
supersession
supersedes MAGNOLIA-5920 Deprecate methods in User interface w... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:
Sprint: Basel 96, Basel 97, Basel 98, Basel 99, Basel 100
Story Points: 13

 Description   

In particular MgnlUser.getAllRoles() dynamically query all groups and all roles to flatten it up on every call. Since user object lasts for the duration of user life time and relogin is required to repopulate it, this info should be cached, either lazily upon first call or eagerly upon creation of the user object when normal group info is also populated.

For details see https://wiki.magnolia-cms.com/display/DEV/Concept+-+Improvements+in+the+security+package#Concept-Improvementsinthesecuritypackage-3.MgnlUserbeanconsistency


Generated at Mon Feb 12 04:20:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.