Magento 2 Integration Resources Aren't Respected

[AngelsDustz]

Preconditions (*)

1. Magento 2.4.2-p1

Steps to reproduce (*)

1. Create a new integration
2. Give it limited right (catalog -> inventory -> products)

3. Do not give it access to "Update Attributes"

Expected result (*)

1. The API is not allowed to update product attributes.
2. Some 403/401 error is returned by the API.

Actual result (*)

1. The API updates product attributes.

What I believe is happening is that it is getting recursive rights, so if you select products it gets all of it under it too. But I need a read-only integration so it seems natural that if the "Update Attributes" is not checked it can not do that.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @AngelsDustz. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Hotel. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.

[ioweb-gr]

I'm also facing the same issue trying to give read only access. Did you manage to find a workaround?

[AngelsDustz]

Sadly no, it was deemed a security issue and couldn't proceed.

[hostep]

@nathanjosiah

[nathanjosiah]

@magento export issue to Jira project AC as Bug

[github-jira-sync-bot]

❌ You don't have permission to export this issue.

[github-jira-sync-bot]

❌ You don't have permission to export this issue.

[github-jira-sync-bot]

❌ You don't have permission to export this issue.

[nathanjosiah]

I will need to dig a bit with this issue. Looking into how this ACL permission is used revealed that there is actually another permission for updating product attributes that seems to duplicate the one in this ticket.

This new permission was added moved in 2.3.3 to fix a display issue 248b894 but all of the API routes still use that old Magento_Catalog::attributes_attributes (Stores -> Attributes -> Product) for edit operations and the new other old permission Magento_Catalog::update_attributes (Catalog -> Inventory -> Product -> Update Attributes) is used for some of the UI.

From my short research so far it looks like the workaround for this would be to disable the old permission (Stores -> Attributes -> Product) which should prevent write access via API but I can't say for sure without looking into this more.

[m2-assistant]

Hi @engcom-November. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.