DocumentationCommerceTools

ACSD-61103: Failure count not reset to zero after successful customer login through API

Last update: Thu Nov 28 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACSD-61103 patch solves the issue where the failure count in the customer_entity table is not reset to zero after a customer successfully logs in through API endpoints. This patch is available when the Quality Patches Tool (QPT) 1.1.54 is installed. The patch ID is ACSD-61103. Please note that the issue is scheduled to be fixed in Adobe Commerce 2.4.8.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.6-p3

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.6 - 2.4.6-p8
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

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.
  2. Generate a customer token via API, using incorrect details.
  3. Check the failures_num column in the customer_entity DB table for the customer above.
  4. Generate a customer token via API, using the correct details.
  5. Check the failures_num column in the customer_entity DB table for the customer above.

Expected results:

The failures_num column should be reset to 0 after using the correct credentials to generate a customer token via API.

Actual results:

The failures_num column is not reset to 0 after using the correct credentials to generate a customer token via API.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3