[MGNLUI-1282] As an admin, I should be able to set permissions on content so that I can secure content. Created: 16/Jan/13  Updated: 05/Jun/13  Resolved: 03/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: configuration, security app
Affects Version/s: None
Fix Version/s: 5.0

Type: Story Priority: Major
Reporter: Andreas Weder Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: apiteam
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-1496 AbstractJcrNodeAdapter refuses to sav... Closed
depends upon MGNLUI-1473 Workbench only shows node if the node... Closed
depends upon MGNLUI-1474 WorkbenchChooseDialogPresenterFactory... Closed
duplicate
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-1460 Create field for managing URL access ... Sub-task Closed Tobias Mattsson  
MGNLUI-1461 Create field for managing ACLs on wor... Sub-task Closed Tobias Mattsson  
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)
Epic Link: Same As 4.5
Sprint: Beta 3
Story Points: 3

 Description   

The goal is described in this UX design page: http://wiki.magnolia-cms.com/display/UX/How+ACLs+are+defined+to+restrict+access+to+nodes

Development is happening on the 'acls' branch.

Web Access Control

  • We add this as a separate tab with a dedicated field

ACLs

  • Each workspace/ACL will have its own field
  • The label of these fields are the workspace names
  • The fields are created dynamically rather than configuring them, by either:
    • using a dynamic provider, similar to configuration-by-code, or
    • by creating a definition in the edit action, like in pages app for adding components

Update: we're not using a provider to add fields because it would be overwritten when the configuration in workspace changes. Instead the action reads a fresh dialog definition from the workspace and then adds the fields. This also means we don't have to require fields to be clonable.

Choose dialog

  • problem:
    • not all workspaces have an app
    • not all choose dialogs return a path (DAM returns an asset id)
  • solution
    • we construct a choose dialog
      • uses a generic workbench configuration
      • the configuration is build by code


 Comments   
Comment by Andreas Weder [ 15/May/13 ]

Adding link to the UI design page describing the new UI.

Generated at Mon Feb 12 08:45:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.