Product is still visible in catalog search after setting category permission to only logged in customers in magento2.4.6

[Pyaray Afzel]

Preconditions and environment

• Magento 2.4.6

Steps to reproduce

category permission is set to logged-in customers only, but when non-logged-in customers search for any product of this category on the front end the product is visible.

Expected result

if category permission is set to log-in users only then its product shouldn't be displayed for non-logged-in customers,
if a product consists of multiple categories like one category is restricted for non-logged-in customers and one category is allowed for non-logged-in customers then it should display the product on the frontend because it consists of a category whose permission is set to allow for non-logged-in customers. front end

Actual result

No product found matching your query something like that

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]

Hi @afzelarshad. Thank you for your report.
To speed up processing of this issue, 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.

---

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

[m2-assistant]

Hi @engcom-Bravo. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

[Pyaray Afzel]

Magento 2.4.6 Enterprise Edition:
To verify if some customization was causing this issue I Deleted all modules in the app code and changed the theme to Magento Luma. but the issue was still persistent.

[m2-assistant]

Hi @engcom-Dash. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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!

---

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

[Madhusmita Sahu]

Hi @afzelarshad ,

Verified the issue on 2.4-develop in commerce edition and it is not reproducible.

Steps to reproduce:-

1.Go to Catalog ->Categories
2.Choose a Category and Deny to not logged in customers in Category Permissions
3.Save the category and reindex
4.Verify the behaviour for not logged in customers

Please refer the attached screenshot and let us if we are missing something.

Catalog->Categories->Selected a category

For Not Logged in customers it is allowed

We can see the category and product available

For Not Logged in customers it is saved as not allowed

We are not able tp see the category and product available