Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Category Permission Validation with REST API on Magento 2.4.4-p1 (EE) #36328

Open
5 tasks
achourey opened this issue Oct 19, 2022 · 15 comments
Open
5 tasks

Category Permission Validation with REST API on Magento 2.4.4-p1 (EE) #36328

achourey opened this issue Oct 19, 2022 · 15 comments
Assignees
Labels
Adobe Commerce The issue related to the Adobe Commerce(EE) or B2B functionality Area: APIs Component: Api Use with concrete module component label E.g. "Component: Api" + "Catalog" Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: dev in progress Reported on 2.4.5-p1 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@achourey
Copy link

achourey commented Oct 19, 2022

Preconditions and environment

  • Adobe Commerce 2.4.5-p1 & 2.4.4-p1
  • The "Category Permission" feature is not working with REST API

Steps to reproduce

  1. Enable Category permission from "Stores >> Configuration >> Catalog >> Catalog >> Category Permissions" with "Yes for everyone" option to allow categories, add to cart etc . Because this feature is not enabled by default.
  2. Go to any of the product and assign that product into a particular Category
  3. Go to that category and restrict all customer group.
  4. Now use following Rest APIs to add that product for restricted customer groups:
    • POST: /rest/V1/integration/customer/token
    • GET: /rest/V1/carts/mine
    • POST: /rest/V1/carts/mine/items

Expected result

The product should not be added to the cart for the customer because it is restricted.

Actual result

The product added to the cart for the restricted customer and the customer is able to place the order with the restricted product.

Additional information

No response

Release note

No response

Triage and priority

  • 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
Copy link

m2-assistant bot commented Oct 19, 2022

Hi @achourey. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.


⚠️ 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, join the Community Contributions Triage session to discuss the appropriate ticket.

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

@m2-assistant
Copy link

m2-assistant bot commented Oct 19, 2022

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).

    DetailsIf 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.

@engcom-November
Copy link
Contributor

@magento give me 2.4-develop instance with edition ee

@magento-deployment-service
Copy link

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@engcom-November
Copy link
Contributor

engcom-November commented Oct 20, 2022

Verified the issue on Magento 2.4-develop instance with enterprise edition modules enabled and the issue is reproducible. Hence confirming the issue.
image

@engcom-November engcom-November added Component: Api Use with concrete module component label E.g. "Component: Api" + "Catalog" Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Reported on 2.4.5-p1 Indicates original Magento version for the Issue report. Area: APIs Adobe Commerce The issue related to the Adobe Commerce(EE) or B2B functionality Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Oct 20, 2022
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6865 is successfully created for this GitHub issue.

@m2-assistant
Copy link

m2-assistant bot commented Oct 20, 2022

✅ Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@engcom-November engcom-November added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Oct 20, 2022
@Poovarasan-06
Copy link

@magento i am working on this

@Vikaashkarthick-K
Copy link

@magento I am working on this

@Poovarasan-06 Poovarasan-06 removed their assignment Aug 30, 2023
@JettyRohanAditya
Copy link
Contributor

@magento I am working on this

@JettyRohanAditya
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @JettyRohanAditya. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@JettyRohanAditya
Copy link
Contributor

@magento give me 2.4.5-p1-instance

@Vikaashkarthick-K Vikaashkarthick-K removed their assignment Sep 6, 2023
@engcom-Hotel engcom-Hotel moved this to Dev In Progress in High Priority Backlog Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Adobe Commerce The issue related to the Adobe Commerce(EE) or B2B functionality Area: APIs Component: Api Use with concrete module component label E.g. "Component: Api" + "Catalog" Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: dev in progress Reported on 2.4.5-p1 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
Status: Dev In Progress
Development

No branches or pull requests

6 participants