ACSD-67039: Encoding diacritics causes validation failures on rp_token…

Categories

Customer

Components

magento/module-customer, magento/module-eav

Origin

adobe-commerce-support

Since QPT

1.1.68

Issue

Encoding diacritics causes validation failures on rp_token, which is excluded from validation. Diacritics are allowed only for email addresses, as intended.

Steps to reproduce

1. Install the Adobe Commerce 2.4.4 version. 1. Create a customer. 1. Upgrade Adobe Commerce to version 2.4.6 from the 2.4.4 earlier version where the customer was already created. 1. Set the encryption key to env.php = d337b914e91ff703b1e94ba4156aadf0 1. Set the below values into the database for any customer under the customer_entity table: *rp_token = incr4869 *rp_token_created_at = 2021-04-29 20:06:14 1. In the Admin panel, go to Customers > All Customers. 1. Edit the customer for which you just updated the above values. 1. Click Save Customer or Save and Continue Edit.

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

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-67039. On Cloud, add ACSD-67039 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-67039/ 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-67039
• JSON API: /api/v1/patches/ACSD-67039