Failed to update user via rest endpoint in version 2.4.5-p11

[mbg0m3s]

Preconditions and environment

Magento Commerce version 2.4.5-p11
Magento extension-b2b
PHP 8.1

Steps to reproduce

1. Use the /rest/async/bulk/default/V1/customers/me endpoint (PUT) to update a customer
   [ { "customer": { "id": 1, "group_id": 1, "email": "user@example.com", "firstname": "Firstname", "lastname": "Lastname", "store_id": 1, "website_id": 1 } } ]
2. With the bulk uuid returned, query the information received(/rest/default/V1/bulk/{bulkUuid}/detailed-status)
   { "operations_list": [ { "id": 0, "bulk_uuid": "4a4fceda-467a-4215-b4fa-5aea76076b97", "topic_name": "async.magento.customer.api.customerrepositoryinterface.save.put", "serialized_data": "{\"entity_id\":null,\"entity_link\":\"\",\"meta_information\":\"{\\\"customer\\\":{\\\"id\\\":null,\\\"group_id\\\":null,\\\"email\\\":\\\"user@example.com\\\",\\\"firstname\\\":\\\"Firstname\\\",\\\"lastname\\\":\\\"Lastname\\\",\\\"store_id\\\":null,\\\"website_id\\\":null}}\",\"store_id\":\"1\"}", "result_serialized_data": null, "status": 4, "result_message": null, "error_code": null } ], "user_type": 2, "bulk_id": "4a4fceda-467a-4215-b4fa-5aea76076b97", "description": "Topic async.magento.customer.api.customerrepositoryinterface.save.put", "start_time": "2025-02-28 14:24:47", "user_id": 1, "operation_count": 1 }
3. The id, store_id and website_id data are null and when the bulk is executed a new customer is created

Expected result

The data sent must be kept in order to correctly update the client.

Actual result

A new user is created because the fields are null

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @mbg0m3s. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[mbg0m3s]

We have identified that we were previously using the API incorrectly to mass update users via the bulk endpoint. This approach allowed us to modify data for multiple users simultaneously, which was not in line with the system's security and integrity rules.

With the API update, a new security layer was implemented that restricts the update to only the authenticated user in the request. This means that any attempt to update a user other than the one logged in will no longer be allowed. If such a request is sent, a new user will be created instead of modifying the existing one.

To avoid this unexpected behavior, a specific treatment could be implemented to invalidate the request and alert the user about the incorrect update attempt. This way, we ensure greater security and consistency in the data handled via the API.