QUALITY PATCH

ACSD-61103: The failure count in the customer_entity table does not reset to zero even…

The failure count in the customer_entity table does not reset to zero even after a customer logs in successfully through API endpoints. Quality patch ACSD-61103 for magento/framework applies to Magento Open Source and Adobe Commerce 2.4.6 to 2.4.6-p15.

Categories
Customer, Web API
Components
magento/framework, magento/module-customer, magento/module-customer-graph-ql, magento/module-integration
Origin
adobe-commerce-support
Since QPT
1.1.54

Issue

The failure count in the customer_entity table does not reset to zero even after a customer logs in successfully through API endpoints.

Steps to reproduce

1. Create a customer account. 1. Generate a customer token via API, using incorrect details. 1. Check the failures_num column in the customer_entity DB table for the customer above. 1. Generate a customer token via API, using the correct details. 1. Check the failures_num column in the customer_entity DB table for the customer above.

Adobe's page lists 2.4.6 - 2.4.6-p8 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.8.

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-61103. On Cloud, add ACSD-61103 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-61103/ 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

Packages across compatible versions (4): magento/module-customer, magento/module-customer-graph-ql, magento/module-integration, magento/framework
Packages across compatible versions (4): magento/module-customer, magento/module-customer-graph-ql, magento/module-integration, magento/framework

magento/magento2-base >=2.4.6 <2.4.7

Magento Open Source
2.4.6-p15, 2.4.6-p14, 2.4.6-p13, 2.4.6-p12, 2.4.6-p11, 2.4.6-p10, 2.4.6-p9, 2.4.6-p8, 2.4.6-p7, 2.4.6-p6, 2.4.6-p5, 2.4.6-p4, 2.4.6-p3, 2.4.6-p2, 2.4.6-p1, 2.4.6
Adobe Commerce
2.4.6-p15, 2.4.6-p14, 2.4.6-p13, 2.4.6-p12, 2.4.6-p11, 2.4.6-p10, 2.4.6-p9, 2.4.6-p8, 2.4.6-p7, 2.4.6-p6, 2.4.6-p5, 2.4.6-p4, 2.4.6-p3, 2.4.6-p2, 2.4.6-p1, 2.4.6
Patch file
patches/os/ACSD-61103_2.4.6-p3.patch
  • vendor/magento/module-customer/Model/Authentication.php
  • vendor/magento/module-customer/Model/Customer.php
  • vendor/magento/module-customer/Model/CustomerAuthUpdate.php
  • vendor/magento/module-customer-graph-ql/etc/graphql/events.xml
  • vendor/magento/module-integration/etc/webapi_rest/events.xml
  • vendor/magento/module-integration/etc/webapi_soap/events.xml
  • vendor/magento/framework/ObjectManager/ResetAfterRequestInterface.php (added)

Sources

Łukasz Bajsarowicz
Built by

Łukasz Bajsarowicz, e-commerce architect

Magento and Adobe Commerce architecture, upgrades, performance and audits for merchants and agencies since 2015; magento.watch is the tooling I use on those projects.

Open source, maintained on weekends.