[MAGNOLIA-6855] Audit logs delete actions in DAM as superuser Created: 01/Nov/16  Updated: 02/Oct/23  Resolved: 02/Oct/23

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 5.3.17
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Nicole Stutz Assignee: Andrew Warinner
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Hi there, we just found a deleted tree in the DAM workspace, luckily it was not published yet. The assets are needed and could be "restored to previous version". Now we wanted to check who did it. Checking the magnolia-audit showed when it happened, but in the name of the superuser. Which didn't do it.

In general all delete actions in the DAM are assigned to the superuser. Delete actions in the website Workspace are assigned to the user, who did it.

Is there an open issue already for this? Maybe already fixed in a higher Version? Or a workaround?

thx, Daniel



 Comments   
Comment by Daniel Stutz [X] (Inactive) [ 01/Dec/16 ]

Hi Andrew

The same thing is with Publishing/Depublishing jobs. All activations are recorded as superuser in Magnolia-audit.log (Activation Tool), well, general in all logs. But activities like copy/create/modify show the username

Example, I just did this in my context (nicstu), but in the log the activations are shown as
01.12.2016 09:38:05 – Exchange: activation succeeded [/public/de]
01.12.2016 09:38:07 – Exchange: activation succeeded [/public/de/impressum/teaserarchive]
01.12.2016 09:38:07 – Exchange: activation succeeded [/public/de/about/portrait/weihnachten]

It is probably related to MAGNOLIA-5473. That issue is closed and declared as fixed with 5.x

Do you know, if this is fixed with > 5.4 ?

Regards, Nicole

Comment by Andrew Warinner [ 01/Dec/16 ]

Hello Nicole,

As you point out, MAGNOLIA-5473 shows that this should have been fixed in the Magnolia 5 branch and be present in 5.3 and 5.4.

I am looking into the source code to see where it went missing.

Comment by Laura Delnevo [ 02/Oct/23 ]

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:18:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.