[MAGNOLIA-6545] DAM: Activation: Log File writes "superuser" in Activation Message when logged in with a different user Created: 11/Feb/16  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 5.4.4
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Tom Wespi Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CE / EE


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
Date of First Response:

 Description   

As the Log Files are the ONLY reference who activated when which asset, we WOULD LIKE TO KNWO THE USERNAME.

As everyone can see this is a state which is very dangerous.

When logged in with a normal user (e.g. Editor), the Log File writes as User "superuser" in the activation message.

This only happens (as far I can tell at the moment) in the DAM App. In Pages and customs apps the correct Username is used.

Log File when activated a asset from DAM with user editor
2016-02-11 16:03:16,103 INFO info.magnolia.module.activation.ReceiveFilter : User superuser successfuly activated page-pics on ROOT. (uri:/.magnolia/activation)
2016-02-11 16:03:16,109 INFO info.magnolia.module.activation.BaseSyndicatorImpl: Exchange: activation succeeded [/system/page-pics] (uri



 Comments   
Comment by Jan Haderka [ 18/Feb/16 ]

As the Log Files are the ONLY reference who activated when which asset, we WOULD LIKE TO KNWO THE USERNAME.

Log files are just log files. If you want to audit activation, you should enable auditing.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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