MDVA-43178: Customer token for a custom store cannot be retrieved in GraphQL

Categories

Web API

Components

magento/module-login-as-customer-graph-ql

Origin

adobe-commerce-support

Since QPT

1.1.14

Issue

Customer token for a custom store cannot be retrieved in GraphQL.

Steps to reproduce

1. Create two Store Views for the default store. 1. Create a new Website, one Store, and one Store View. Name this Store View 'test3'. 1. Create a customer for the new website. 1. Generate API admin token: http://domain/rest/all/V1/integration/admin/token <pre> <code class="language-graphql"> { "username": "login", "password": "password" } </code> </pre> 1. Send GraphQL to retrieve customer token as an admin, use the admin token for authorization, with "store" = "test3" in the header: <pre> <code class="language-graphql"> mutation{ generateCustomerTokenAsAdmin(input: { customer_email: "<customer_email>" }){ customer_token } } </code> </pre>

Adobe's page lists 2.4.3-p1 - 2.4.4 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.4.5.

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 MDVA-43178. On Cloud, add MDVA-43178 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its MDVA-43178/ 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 MDVA-43178
• JSON API: /api/v1/patches/MDVA-43178