[MGNLPUR-65] UserManager for public does not have a realmName property Created: 23/Mar/12  Updated: 17/Jul/14  Resolved: 05/Jun/14

Status: Closed
Project: Magnolia Public User Registration
Component/s: config
Affects Version/s: 1.4.1, 2.0
Fix Version/s: 1.4.7, 2.2.4, 2.3

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Karel Nedoma
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File screenshot-public-realmName.png    
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,

I'm not sure if this is actually a bug or if it's intentional. But when comparing the configurations for the different userManagers I noticed that the public content node does not have a realmName property set like the others. See attached screenshot taken from demoauthor.magnolia-cms.com.

Let me know if you have any questions.

Cheers,
Matt



 Comments   
Comment by Philipp Bärfuss [ 26/Mar/12 ]

As far I know this is a bug.

Comment by Roman Kovařík [ 05/Jun/14 ]

Reopen:

  1. Please update also the bootstrap file.
  2. Type in the test name testUpgradeFrom222TreeNodeExiss. What is the purpose of this test anyway. Isn't it redundant?
  3. Add more explanatory task name (e.g. same as in the inner task)
    .addTask(new NodeExistsDelegateTask("Create new property" 
    
Comment by Roman Kovařík [ 05/Jun/14 ]

Review: please squash/rebase to a single commit when integrating.

Generated at Mon Feb 12 06:42:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.