[MAGNOLIA-6618] add default web access to some roles Created: 30/Mar/16  Updated: 19/May/22  Resolved: 19/May/22

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

Type: Improvement Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

EE Standard 5.4.5 installed without demo


Attachments: PNG File Magnolia_5.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)
Date of First Response:

 Description   

When 5.4.5 is installed without demo (there is no Eric or Peter user and no demo roles). In this setup there is no role (well there is on, but ... "scripter") with "web access": . That means if you add new user and give him any standard role like editor, publisher, etc... he can't login into admincentral until you go edit any of this roll and add this "web access": to any of them.

Which may be confusing for someone who is first time playing with users and roles...



 Comments   
Comment by Jan Haderka [ 30/Mar/16 ]

But aren't those roles (editor, templater) created by demo?
And isn't there security-base role that should be enough to be assigned to the user.

Comment by Tomáš Gregovský [ 31/Mar/16 ]

Not sure from which module is "editor" role, but demo provides "travel-demo-editor" and bunch of other roles, which are not there if you install Magnolia without travel demo. For example demo user "Eric" has assigned group travel-demo-editors and one of roles in this group is travel-demo-admincetral, which gives Eric this "web access":* which means he is able log into admincentral, but without travel-demo installed these is no similar role.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:16:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.