View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007725 | OXID eShop (all versions) | 1.05. Users | public | 2024-09-25 09:02 | 2024-09-27 15:25 |
| Reporter | bYemma | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 7.1.0 | ||||
| Summary | 0007725: Should admin usergroup be assigned for new admin account? | ||||
| Description | After creating a new admin account on the console, the user is not assigned to usergroup "Shop-Admin". I think that would be a useful extension. | ||||
| Steps To Reproduce | Used command for creating new admin user: ./vendor/bin/oe-console oe:admin:create-user --admin-email=xyz --admin-password='xyz' | ||||
| Tags | No tags attached. | ||||
| Theme | All | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
Hi @bYemma, thank you for your report! I've checked the case if the administration area does assign a new user, flagged as admin, to the oxidadmin group, but it doesn't. As far as I can see there are pieces of test data left over in the Codeception tests (https://github.com/OXID-eSales/oxideshop_ce/blob/c7fffe8b2143ad8dc4c7598a9baecec174ad77ba/tests/Codeception/Support/Data/dump.sql#L54), but the framework doesn't add a new admin user to this very group. So I classify this as a feature request (as I can imagine it could be useful to have an automated workflow (e.g. If this event happens, then do that)). That's why I'm closing this bug entry but I've forwarded the feature request to our Requirements Engineer. Kind regards Michael Keiluweit |
|
|
Just a note: GraphQL uses the user groups to authorize the users. That affects also administrator relevant actions. For that the documentation states to make use of the group oxidadmin: https://docs.oxid-esales.com/interfaces/graphql/en/latest/authorization.html#id1 |
