[MAGNOLIA-1747] Missing group reported when starting magnolia without the samples module Created: 23/Sep/07  Updated: 23/Jan/13  Resolved: 13/Oct/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.1 M3
Fix Version/s: 3.5 RC1

Type: Bug Priority: Major
Reporter: Fabrizio Giustina Assignee: Magnolia International
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1164 Clean up default users/groups/roles Closed
duplicate
duplicates MAGNOLIA-1680 Exception thrown when samples module ... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When starting magnolia on the current trunk without the samples module installed you get a lot of logs like the following:

ERROR info.magnolia.cms.security.MgnlSecurityUtil MgnlSecurityUtil.java(collectPropertyNames:87) 23.09.2007 11:47:46 Can't find usergroups node by UUID ea7603eb-fa77-4a81-97e4-906f6da22588 referred by node /system/superuser/groups/0

this is due to the group publisher, which is only added by the samples module (usergroups.publisher.xml) but is also added by default to the superuser user.



 Comments   
Comment by zam6ak [ 24/Sep/07 ]

I think this issue relates to http://jira.magnolia.info/browse/MAGNOLIA-1680

The 2 groups required for workflow, should be bootstrapped by the workflow module and not samples module.

Comment by Magnolia International [ 08/Oct/07 ]

related to this and your commit r11439, what do you mean with the "todo" comment you added: "why we are using UUIDs here? shouldn't be better to use group names, since uuids can change" ?

Comment by Philipp Bracher [ 09/Oct/07 ]

In the realm of security it would make sense to store the names since this are the names are the keys. You actually don't care if you rename a role to anonymous or recreate a certain role. But since we store the uuid this would not work.

Another pitfall I see is if you store the groups externally. How would you match them to uuids?

Comment by Magnolia International [ 13/Oct/07 ]

Ok, so here's how I "fixed" this. Let me know what you think + if it solves your issues.

Sample module now has

  • users
  • bob
  • joe
  • melinda
  • groups
  • developers
  • employees
  • roles
  • base
  • developer
  • editor
  • securitymanager

Workflow module has

  • groups
  • editors
  • publishers

Joe and Melinda are assigned to the editors and publishers groups respectively upon installation of the workflow module, if the sample module is present in the system. (installed previously or being installed at the same time)

The defaut activation workflow definition was adapted to match the new group names. (plural form)

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