new group privileges

[GülsümAkça]

hello. I created a new group . I want the new group to see only the product and order panel. how can i do that? thank you

[aimeos]

Overwrite the permission configuration and add your group to the panels you want to allow:
- https://aimeos.org/docs/latest/admin/jq ... ermissions
- https://github.com/aimeos/ai-admin-jqad ... source.php

You must give the group acess to the dashboard too because it's the first panel that is shown.

[GülsümAkça]

hello, except for what you said, it is necessary to write code in the config/shop.php file, otherwise it gives an authorize error (413).
Added and solved, thanks.

Code: Select all

'roles' => [ 'editor' , 'admin' , 'mynewgroup' ]

[nowrap]

Hello and thanks for this guide so far.

I have two questions/problems.

I added to config/shop.php:

• 'admin/jqadm/resource/dashboard/groups' => ['newgroup']

• 'admin/jqadm/resource/order/groups' => ['newgroup']

• 'roles' => ['editor', 'admin','newgroup']

If i login to /admin with a test user the dashboard isn't shown as default. But i can access it manually with /admin/default/jqadm/search/dashboard. How can the dashboard be the first view after login?

And i can an error (403) for this request in the dev console of the browser:
/admin/default/jsonadm

I tried to add to config/shop.php:

• 'admin/jsonadm/resource/index/groups' => ['newgroup']

But the error is still present.

[aimeos]

I added to config/shop.php:

• 'admin/jqadm/resource/dashboard/groups' => ['newgroup']

• 'admin/jqadm/resource/order/groups' => ['newgroup']

• 'roles' => ['editor', 'admin','newgroup']

If i login to /admin with a test user the dashboard isn't shown as default. But i can access it manually with /admin/default/jqadm/search/dashboard. How can the dashboard be the first view after login?

Did you try to add all groups instead?

Code: Select all

['super', 'editor', 'admin','newgroup']

And i can an error (403) for this request in the dev console of the browser:
/admin/default/jsonadm

I tried to add to config/shop.php:

• 'admin/jsonadm/resource/index/groups' => ['newgroup']

The JSON admin API is restricted to the configured groups for each endpoint. You need to make sure that your new group has access to all API endpoints that are used by the allowed panels. Here's the default configuration:
https://raw.githubusercontent.com/aimeo ... source.php

[nowrap]

Thx for your reply.

I added the other groups to the config/shop.php but this doesn't change the behaviour to automatically navigate to the admin dashboard view. It opens the /profile page.

The request to /admin/default/jsonadm?locale=de is an options request. I tried to follow the source code to find the origin of the exception for the 403 response. It's the JsonadmController.php in method optionsAction:
https://github.com/aimeos/aimeos-larave ... r.php#L116

There the groups seems to be hardcoded?

Code: Select all

$this->authorize( 'admin', [JsonadmController::class, ['admin', 'editor', 'api']] );

For testing i added my new group. After this the request finishes. But i still have a lot of spinning icons. Only the newest orders are presented correctly.

dashboard.png (102.38 KiB) Viewed 23976 times

Regards
nowrap

[aimeos]

Yes, the fixed auth groups for the Laravel Jsonadm controller are a problem for adding new groups. We've already thought to make that configurable. Would that be sufficient to finally add new backend groups?

[nowrap]

For us we have only two wishes:

• option to configure which admin views are accasible for a new group

• set an admin page as standard view after login for a new group

[aimeos]

• option to configure which admin views are accasible for a new group

• set an admin page as standard view after login for a new group

The Aimeos 2023.07.1 package released today contains two settings which allows you to configure the groups that are allowed to access the admin backend (incl. JSON admin API) and the default panel. In the ./config/shop.php use:

Code: Select all

	'roles' => ['admin', 'editor', 'newgroup'],
	'panel' => 'order',

Enjoy!

[nowrap]

Thx, alot!

Sorry for answering so late. So we have to upgrade from 2022.x to 2023.x first in order to use this improvement.