[MAGNOLIA-3027] Use factory to instantiate AccessManager to allow swapping implementations Created: 19/Jan/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Improvement Priority: Major
Reporter: Vivian Steller Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: 0.25h
Time Spent: Not Specified
Original Estimate: 0.25h

Attachments: Text File access-manager-factory.patch    
Issue Links:
duplicate
is duplicated by MAGNOLIA-4086 security: introduce AccessManagerProv... Closed
Template:
Patch included:
Yes
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)
Date of First Response:

 Description   

AccessManager gets instantiated via new AccessManagerImpl in WorkspaceAccessUtil:createAccessManager(...) preventing from swapping the implementation in custom modules.

Tests run through, however, please verify info.magnolia.context.SystemRepositoryStrategyTest

Thanks!



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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