"User type not defined" error when using OAuth1 authentication on guest cart endpoints

[karitham]

Preconditions and environment

• Magento version: 2.4.7
• Backpressure enforcement enabled (sales/backpressure/enabled = 1)
• OAuth1 integration configured with valid consumer key/secret
• REST API webapi_rest area

Steps to reproduce

1. Enable backpressure
2. Create a guest cart via REST API: POST /rest/V1/guest-carts
3. Add products and set shipping information
4. Attempt to place order using OAuth1 authentication:

   POST /rest/V1/guest-carts/{cartId}/payment-information
   Authorization: OAuth....
   Content-Type: application/json
   
   {
     "email": "customer@example.com",
     "paymentMethod": {"method": "checkmo"}
   }
   

Expected result

Order should be placed successfully with a valid order ID returned, or appropriate validation errors if payment/shipping data is invalid.

Actual result

API returns error:

{"message":"User type not defined"}

Exception is thrown from Magento\Authorization\Model\IdentityProvider::fetchIdentityType() at line 65.

Additional information

I am an API client integrating against major hosted magento2 websites and we recently started having this error; I do not host or own myself a magento2 instance.

I'm not that proficient at PHP so bear with my analysis here:

Root Cause:

The IdentityProvider class only maps two user types for backpressure rate limiting:

• USER_TYPE_CUSTOMER → IDENTITY_TYPE_CUSTOMER
• USER_TYPE_ADMIN → IDENTITY_TYPE_ADMIN

However, when OAuth1 authentication is used, the OauthUserContext returns USER_TYPE_INTEGRATION (value 1), which has no mapping.

This causes the RuntimeException.

Affected code:

app/code/Magento/Authorization/Model/IdentityProvider.php lines 24-27:

private const USER_CONTEXT_IDENTITY_TYPE_MAP = [
    UserContextInterface::USER_TYPE_CUSTOMER => ContextInterface::IDENTITY_TYPE_CUSTOMER,
    UserContextInterface::USER_TYPE_ADMIN => ContextInterface::IDENTITY_TYPE_ADMIN
    // Missing: USER_TYPE_INTEGRATION mapping
];

Release note

Fixed "User type not defined" error when calling guest cart REST API endpoints with OAuth1 authentication and backpressure enabled.

Triage and priority

• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.

[m2-assistant]

Hi @karitham. 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.