[MAGNOLIA-2730] Reimplement audit and security using HierarchyManagerWrapper, ContentWrapper, etc. Created: 14/May/09  Updated: 27/Nov/13  Resolved: 03/May/13

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

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2826 Audit logs a "logout" action as being... Closed
is related to MAGNOLIA-2732 Move NodeDataWrapper from STK to core Closed
is related to MAGNOLIA-2599 Make audit logging fully configurable Closed
is related to MAGNOLIA-2833 Audit login and logout operations in ... Closed
is related to MAGNOLIA-4778 Audit log is (partially) not working ... 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)

 Description   

This would simplify:

  • the code itself (less redundancy, less error-prone - an AuditingHM would do one single thing (audit logging) and delegate)
  • turning these features on/off
  • replacing/customizing them
  • tests (because I don't want to have audit log in my tests, nor have to configure them)

We already have RepositoryAcquiringStrategy, which is where the appropriate wrappers w/c/ould be constructed.

It would also serve as a proof of concept for more advanced uses of wrappers (which I will dutifully note here once I remember them)



 Comments   
Comment by Magnolia International [ 03/May/13 ]

MAGNOLIA-4778 reimplemented audit logging using wrappers; security is now applied at JCR level.

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