[MAGNOLIA-4366] Delta for 4.5.2 update may remove realmName property from userManagers entirely Created: 03/Apr/12  Updated: 24/May/12  Resolved: 14/May/12

Status: Closed
Project: Magnolia
Component/s: core, security, updatemechanism
Affects Version/s: 4.5.2
Fix Version/s: 4.5.3

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: core, security, update
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-4069 Delta for 4.5 update contains typos i... 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   

Hi,

The fix for MAGNOLIA-4069 may have an unfortunate consequence if the realName property isn't found, and instead a realmName property already exists, then the MoveAndRenamePropertyTask sets realmName to a null value.

Perhaps, the MoveAndRenamePropertyTasks should be wrapped within a PropertyExistsDelegateTask ?

Let me know if you have any questions.

Cheers,
Matt



 Comments   
Comment by Ondrej Chytil [ 05/Apr/12 ]

Thanks for reporting Matt, this will be fixed in next release.

Comment by Ondrej Chytil [ 14/May/12 ]

Commit.

Comment by Jan Haderka [ 24/May/12 ]

Git link's broken!

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