-
Bug
-
Resolution: Fixed
-
Neutral
-
5.3.9, 5.4.7
-
-
Empty show more show less
-
Kromeriz 54
-
5
When a system user changes the password of any user through Security app, no track of the system user that made the change is stored in log-audit, always systemUser is set.
It seems that the update is being done in the system context and because of that reason the user is not being written down:
private static String getUser() { if (MgnlContext.isSystemInstance()) { return "SystemUser"; } try { if(MgnlContext.hasInstance() && MgnlContext.getUser() != null) { return MgnlContext.getUser().getName(); } }catch (Exception e) { return "system user"; } return "user not set"; }
I tested it in Magnolia 5.3.9 and Magnolia 5.4.7 (demoauthor.magnolia-cms.com)
More information can be found in linked ticket (SUPPORT-6040)
- is causing
-
MAGNOLIA-6731 Some operations are requested to run in system context while already in system context
- Accepted
-
MAGNOLIA-6734 Assess and clean up redundant system context executions
- Closed
-
MAGNOLIA-6798 Reduce log level from warn to debug until MAGNOLIA-6731 resolved
- Closed
- is depended upon by
-
MGNLUI-3961 Adjust test to changes in MAGNOLIA-6686
- Closed