How to give admin panel access to additional user group

[VirtualSpy]

laravel version 9.48.0 , Aimeos version 2022.10.4 and PHP version 8.1.3 (Win)

i have created two additional group one for catalog management and one for order management , i know about permission for group https://github.com/aimeos/ai-admin-jqad ... source.php but i didn't get how to give access to additional groups.

[aimeos]

Access to panels is checked here:
https://github.com/aimeos/ai-admin-jqad ... hp#L45-L47

Just add the names of your additional groups in your ./config/shop.php for order and user panels:
- https://github.com/aimeos/ai-admin-jqad ... hp#L30-L55
- https://github.com/aimeos/ai-admin-jqad ... p#L73-L115

[VirtualSpy]

Access to panels is checked here:
https://github.com/aimeos/ai-admin-jqad ... hp#L45-L47

Just add the names of your additional groups in your ./config/shop.php for order and user panels:
- https://github.com/aimeos/ai-admin-jqad ... hp#L30-L55
- https://github.com/aimeos/ai-admin-jqad ... p#L73-L115

Thanks for your response, I understood this, but I am not able to login in admin panel by additional customer group's email, I checked with SHOP_PERMISSION in env by adding an additional customer group code, but it is showing This action is unauthorized.

[VirtualSpy]

Access to panels is checked here:
https://github.com/aimeos/ai-admin-jqad ... hp#L45-L47

Just add the names of your additional groups in your ./config/shop.php for order and user panels:
- https://github.com/aimeos/ai-admin-jqad ... hp#L30-L55
- https://github.com/aimeos/ai-admin-jqad ... p#L73-L115

Thanks for your response, I understood this, but I am not able to login in admin panel by additional customer group's email, I checked with SHOP_PERMISSION in env by adding an additional customer group code, but it is showing This action is unauthorized.

Aimeos ! Did you understand my problem?

[VirtualSpy]

Aimeos ! Will you reply? Thanks in Advance

[aimeos]

Guess, the problem is the fixed list of groups here:
https://github.com/aimeos/aimeos-larave ... er.php#L36

If it would be configurable, you can log in with users having different groups.

[VirtualSpy]

Guess, the problem is the fixed list of groups here:
https://github.com/aimeos/aimeos-larave ... er.php#L36

If it would be configurable, you can log in with users having different groups.

It was helpful, and because of this, I knew more. https://github.com/aimeos/aimeos-larave ... roller.php in this controller one configuration is using

Code: Select all

if( config( 'shop.authorize', true ) ) {
			$this->authorize( 'admin', [JqadmController::class, config( 'shop.roles', ['admin', 'editor'] )] );
		}

Because of this config it was showing This action is unauthorized. so, I used this config in config/shop.php .
but now I want to know the best way to overwrite the controllers because I want to overwrite https://github.com/aimeos/aimeos-larave ... er.php#L36 this controller.

[VirtualSpy]

Guess, the problem is the fixed list of groups here:
https://github.com/aimeos/aimeos-larave ... er.php#L36

If it would be configurable, you can log in with users having different groups.

It was helpful, and because of this, I knew more. https://github.com/aimeos/aimeos-larave ... roller.php in this controller one configuration is using

Code: Select all

if( config( 'shop.authorize', true ) ) {
			$this->authorize( 'admin', [JqadmController::class, config( 'shop.roles', ['admin', 'editor'] )] );
		}

Because of this config it was showing This action is unauthorized. so, I used this config in config/shop.php .
but now I want to know the best way to overwrite the controllers because I want to overwrite https://github.com/aimeos/aimeos-larave ... er.php#L36 this controller.

I have overwritten the controller and route from Laravel, if you have any other way to overwrite it please share.

[aimeos]

It would be best if the roles in the AdminController could be configured like in the JqadmController with:

Code: Select all

config( 'shop.roles', ['admin', 'editor'] )

Then, you can configure which roles can be used for the backend. If you can create a PR, we will be happy to merge it and port it back to 2022.10