ACSD-57570: A restricted admin user with access to a particular store cannot always see all shared…

Categories

B2B, Admin

Components

magento/module-shared-catalog, magento/module-admin-gws, magento/module-support, magento/module-customer, magento/module-user

Origin

adobe-commerce-support

Since QPT

1.1.57

Issue

A restricted admin user with access to a particular store cannot always see all shared catalogs or save customers, leading to inconsistencies. With multiple stores, the restricted admin cannot see new companies or custom shared catalogs.

Steps to reproduce

1. Set up stores in the following order: * Create a new website named W2. * Create a new store view for the default website. * Create a new store named W2S2 for website W2. * Create a new store view named W2S2SV1 for the store W2S2. * Create another new store view named W2S2SV2 for the store W2S2. * Create a company for W2. 1. Assign products: * Assign some products to W1 only. * Assign some products to W2 only. * Assign some products to both W1 and W2. 1. Create a custom shared catalog and assign all products to it. 1. Create a custom admin role with access to only W2S2, not W2. 1. Assign the restricted admin user to the new custom admin role. 1. Log in as the restricted admin user. 1. Verify access: * Check which companies you can see. * Check which shared catalogs you can see. * Open the products list and verify if you can see all the shared catalogs to which the products are assigned.

Adobe's page lists 2.4.3 - 2.4.4-p9 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.5.0.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACSD-57570. On Cloud, add ACSD-57570 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACSD-57570/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.

Patch files and compatible versions

Sources

• Adobe documentation for ACSD-57570
• JSON API: /api/v1/patches/ACSD-57570