umasked quote_id being passed when calling estimate-shipping-methods API in checkout page

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

Open Software License 3.0

11.5k stars 9.3k forks source link

Preconditions (*)

Magento 2.4.3-p1

Steps to reproduce (*)

Login to storefront as a regular customer
Add few items into the cart
Click on "Proceed to checkout"
Checkout page renders on the browser
API call to rest/home3/V1/guest-carts/22806/estimate-shipping-methods where 22806 is the unmasked quote_id

Expected result (*)

Checkout as registered customer
Able to proceed to get shipping quote. Call API rest/home3/V1/guest-carts//estimate-shipping-methods using the masked quote ID (hashed ID)
Redirect to payment page and complete the order

Actual result (*)

Checkout page doesn't recognize the login session, it is checking out as guest identity
Call estimate-shipping-methods with unmasked quote_id provided
API response with error No such entity because of unmasked quote_id doesn't exists in masked quote mapping table

Additional Information

the properties window.checkoutConfig.quoteData.entity_id has stored a unmasked value

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

[x] 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”.

Hi @vicehope. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

magento / magento2