[MAGNOLIA-5061] Allow configuring the workspace on MgnlUserManager Created: 24/May/13  Updated: 10/Mar/21  Resolved: 10/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Tobias Mattsson Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: next
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)

 Description   

To use MgnlUserManager, or HierarchicalMgnlUserManager for that matter, with a workspace other than 'users' currently you have to override both getRepositoryName() and getHierarchyManager(). If the repository/workspace name was configurable instead this wouldn't be necessary,

Also getHierarchyManager() should call getRepositoryName() instead of always using 'users', thereby requiring subclasses to override it if they want to use a different workspace.

The default repository/workbench should still be 'users' when not configured of course.

The use case here is for a clustered workspace with public users.


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