[MAGNOLIA-1164] Clean up default users/groups/roles Created: 26/Oct/06  Updated: 23/Jan/13  Resolved: 13/Oct/07

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

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-1680 Exception thrown when samples module ... Closed
is depended upon by MAGNOLIA-1747 Missing group reported when starting ... Closed
relation
is related to MAGNOLIA-1680 Exception thrown when samples module ... Closed
supersession
is superseded by MAGNOLIA-2165 Improve sample user names 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)

 Description   
  • some groups have irrelevant roles (for instance group "editor" currently has the "superuser" role !!)
  • most names could be improved :
    • avoid duplicate names (for instance there currently is a user, a group AND a user called "editor")
    • group names could be of the plural form, to make it more obvious they're groups of users
    • users might have "real" names (joe, ...) to avoid confusion with groups/roles


 Comments   
Comment by Magnolia International [ 26/Oct/06 ]

"Joe is in department A"

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:24:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.