GraphQL product search does not consider Category Permissions configuration

[magento-engcom-team]

GraphQL product search does not consider Category Permissions on category level and in System Configuration (Stores > Configuration > Catalog > Catalog > Category Permissions)

Preconditions

1. Install 2.3-develop
2. Create product Apple in category sub with price $10
3. Go to Stores > Configuration > Catalog > Catalog > Category Permissions
4. Set Enable to Yes and leave all other options as is (it means that all categories and products will be hidden for all customers or not logged in users)
5. Save Config and clear cache
6. Make sure that category sub is not accessible from the storefront as well as simple product Apple by direct URL

Steps

1. Send GraphQL request:

query{
products(search: "Apple"){
	items {    
		name
		price {
			minimalPrice {
				amount {
					value
					currency
					}								
				}
			}  
		sku
	}
	total_count
	}
}

(-) The response contains data of product Apple

(+) Not enough permissions error message displayed

[m2-assistant]

Hi @magento-engcom-team. 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.

[m2-assistant]

Hi @pmarjan. 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!

---

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

[magento-engcom-team]

Hi @magento-engcom-team. Thank you for your report.
The issue has been fixed in #28757 by @pmarjan in 2.4-develop branch
Related commit(s):

• 308ef0e7932653cfedfdc1cc3176da3b8b8faaec
• 332369d81ca99be42514df19f0aaaa84c8ee96c4
• 966aeba8a4c06712710d13bc74ed752ab2b8bbac
• 191b758e017b57d46ddb700cee48b5eaeaf37990
• a5e978e0cca31600bcce04a785620f58d800c4a0
• c53526484b93d75349cfe815fd214f95c255f171
• ea0ea52ae770656486ab5636ad678f7c72646dc0
• 48f9256644cb8cb45aea864af3aec4242901ed30
• 4ed80e3fdfd8280e2c13d7a86f348e21cf2fd3bd
• d0f34159af28b182a644cceac245a0262dc165cf
• a675e30bef1d7eca234531b4bfcca611a3979229
• c689798c58e6be2232164be9035d08c79e1f15e3
• d127628de669799f24e6f72bf5dff285fc3879a4
• a87a88dfb508f31fb655c93af0b88a110a86b52a

The fix will be available with the upcoming 2.4.1 release.