Admin panel is not accessible after limited permissions set to at least one admin account

[sivaschenko]

Preconditions (*)

Magento is installed

Steps to reproduce (*)

• Login to admin panel
• Go to System->User Roles
• Create a new role:
• In Role Resources check only Media Gallery
  
• Create a new admin user account and assign the created role to it
• Log out from admin panel
• Log in to admin panel as a newly created user
• Log in to admin panel as an admin having full permissions

Expected result (*)

The new admin user is logged into the admin panel.
Other admin accounts are not affected.

Actual result (*)

User is redirected to frontend page with status code 404.
Admin panel is not available for other admins with full permissions

Additional Info

The issue can be reproduced if admin user role includes only ACL resources that are not associated with page/menu item in the admin panel

[m2-assistant]

Hi @sivaschenko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@sivaschenko do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[krishprakash]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-25881-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[krishprakash]

Hi @sivaschenko.
I'm not able to reproduce the issue on 2.3 develop instance as provided steps by you.
I followed the steps below to reproduce the issue:

1. Login to admin panel
2. System > User Roles > Created a new role with only Media gallery permission
3. Create new user and assigned newly created role
4. Logout from main admin
5. Login with newly created admin role
6. Open the private window and login with main admin which have full permission
   Let me know if I missed anything
   Thanks

[krishprakash]

Reproduced in my local vanilla instance.
Can not access the main admin as described in issue description.

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-29321 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @edenduong. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[VladimirZaets]

Hi @sivaschenko. Thank you for your report.
The issue has been fixed in #25909 by @edenduong in 2.4-develop branch
Related commit(s):

• da1daaeeb64f29d7f23bc71e63987ffbc7994099
• 1f12acfbf94dcfc4acaeba7f74e1b78596817213
• 78bf9c21793fec6b3903e59cd1d36a720dfdac29
• b7bc81fc6a4b04c68546096dd07214d50e2aa40d
• 957f056adde00167bbde548b23a3fb190aa72522
• 034a0ed158d3a69da40a3afdee218c20fe33a0e8
• da17c67bc68de7020d777a15aa4ff7f985f7300f
• 468da78a555d0a4dad5c17c8ab5caf8466069bca
• eee523002beb81bb5935bb278c363559daac0f57
• f5db9f664bcc45f18adc54a2987970f27c2cb068
• f07d0e16df431412b70d4a06b06eecfe65c69ad9

The fix will be available with the upcoming 2.4.0 release.