Cannot do POST /V1/carts/mine or PUT V1/guest-carts/{cartId} with Intergation tokens on Magento 2.4.6-p8 and 2.4.4-p12

[ErnestsVerins]

Preconditions and environment

Magento version: 2.4.* ( Tested on 2.4.3, 2.4.4 and 2.4.6)

On Magento 2.3.5 I was able to do POST /V1/carts/mine / POST /V1/carts/mine/items OR PUT V1/guest-carts/{cartId} with Intergation tokens, but on Magento 2.4.* it doesn't work.

Steps to reproduce

1. In admin under System>Extensions>Integrations create a new integration

2. Do POST /rest/default/V1/carts with Auth. type OAuth 1.0, Signature Method HMAC-SHA256 and enter the Integration keys and tokens there. As a result, quote id value will be generated;

3. Do POST /rest/default/V1/carts/mine/items with the same Auth. and with body (add the quote_id that was created with the previous request):

{
"cartItem": {
"sku": "{sku}",
"qty": 1,
"quote_id": {quote_id}
}
}

4. Do POST rest/default/V1/guest-carts with the same Auth. type to get customer quote id.
5. Do PUT rest/default/V1/guest-carts/{cart_id} with the same Auth. and body

{
"customerId": {customer_id},
"storeId": 0
}

Expected result

• POST /rest/default/V1/carts/mine/items - item gets added to the cart
• PUT rest/default/V1/guest-carts/{cart_id} - the customer has been assigned to the specified cart

Actual result

POST /V1/carts/mine / V1/carts/mine/items:

{
    "message": "\"%fieldName\" is required. Enter and try again.",
    "parameters": {
        "fieldName": "customerId"
    }
}

PUT V1/guest-carts/{cartId} :

{
    "message": "You don't have the correct permissions to assign the customer to the cart."
}

Additional information

I'm investigating this, because the third party needs these requests to work with the integration token the same way as on the old setup (2.3.5).

In admin under System>Extensions>Integrations I have created an integration:

• Callback URL is empty;
• Identity link URL is empty;
• Resource Access is All

In admin Stores>Configurations>Services>OAuth>Consumer Settings "Allow OAuth Access Tokens to be used as standalone Bearer tokens" is set to Yes. Expiration Period is set to 30000.

Proposed solution

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 @ErnestsVerins. 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.