[MAGNOLIA-898] Groups: Assigned Roles with ACL are not respected by Magnolia Created: 24/May/06  Updated: 23/Jan/13  Resolved: 06/Jun/06

Status: Closed
Project: Magnolia
Component/s: security
Affects Version/s: 3.0 Beta 1
Fix Version/s: 3.0 RC1

Type: Bug Priority: Blocker
Reporter: Giancarlo Berner Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP, Jetty 6


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   
  • Create a Role with an ACL
  • Create a group and assign the Role
  • Create a user and assign to Group
  • Login as new User
    --> All available nodes are listed (e.g. in DMS)
  • Assign the Role directly to the User
  • Login as new User
    --> Only the noedes allowed in the Role are visible


 Comments   
Comment by Philipp Bracher [ 24/May/06 ]

the core is handling it correctly but the dialogs are crap, respectively storing the data in a wrong way.

doing this we need to consolidate the dialogs as follow:

  • User dialog
  • select the groups as you select the roles
  • store the assigned groups using a similar data structure as for the roles
  • Group dialog
  • select the roles similar to the user dialog
  • a group has not it's own acl's but assigned roles
  • the assigned roles should get stored similar as it is done by the users

If it is urgent you can send us a patch for those dialogs

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