[MGNLWORKFLOW-197] Do not overwrite customer's roles during migration or a standard upgrade. Created: 24/Jan/14  Updated: 04/Feb/14  Resolved: 29/Jan/14

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2, 5.3

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

Issue Links:
causality
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   

Corporate website projects installs its own roles which are in conflict with the new roles introduced in 5 since they are sharing the same name.

As a consequence, editor role is reimported with a different UUID during the migration. Since roles are referenced by UUID, users cannot login.



 Comments   
Comment by Eric Hechinger [ 28/Jan/14 ]

Solution:
For fresh installation and update :

  • Only bootstrap the editor/publisher roles and editors/publishers groups if they are not yet defined.
  • Associate the roles to the groups.
Generated at Mon Feb 12 10:07:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.