[MAGNOLIA-7180] It should be straightforward to create a new user that can log into admincentral Created: 17/Oct/17 Updated: 31/Oct/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.5.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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
|
||||
| Description |
|
It must be straightforward to create new users who can login and perform the standard actions in Magnolia. For example: a user with the editor or publisher role should be able to login to admincentral. Currently, if the travel demo is not installed it is difficult (or at least unclear how) to create a user who can even log in to Magnolia. An administrator will expect that giving a user the bundled "editor" or "publisher" role will allow that user to at least login, and probably perform editing and publishing tasks. But alone, the roles do not do this. A user must also have a special configuration of the "Web access". I do not know the exact configuration necessary, but looking at the "travel-demo-admincentral" role I see a "Get & Post" value of "*". |