logout issue when using Graphql

[estellehuang]

Preconditions and environment

• Magento version 2.4.6-p5

Steps to reproduce

Using Graphql

1. login on frontend
2. logout
3. login again

Expected result

Customer could login successfully

Actual result

The following error message display:

The current user cannot perform operations on cart "QXJscogXHdkTyJLXK0OcItaEByrGivCg"

Additional information

I made some investigation. I found even I logged out. When calling API createEmptyCart, the userid used to create cart is the userid I loged in last time instead of guest 0. The version 2.4.4-p2 doesn't has the issue. I found there is new feature for Graphql. That is disabling session for graphql. But in admin panel, I can't find the area to config it. Graphql session is enabled in default configuration. After I disabled it by changing code, my issue could disappear. I could login and logout without any issue.

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 @estellehuang. 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. 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.
⚠️ 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-Delta. 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[estellehuang]

Hi,

Any progress on this issue?

[engcom-Delta]

Hi @estellehuang ,

Thanks for reporting and collaboration.

We have tried to verify this issue on magento 2.4-develop instance and it is not reproducible.

Steps to reproduce:-

Using Graphql

1.login on frontend
2.logout
3.login again

Please check the video attached and let us know if we missed anything.

We are not getting any errors while logging in again.

Screen.Recording.2024-05-28.at.3.11.04.PM.mov

[engcom-Delta]

Hi @estellehuang ,

Awaiting your reply on this issue to move further.

Thanks,

[engcom-Delta]

Hello @estellehuang ,

As there is no activity on this issue for a long time, we believe the issue has been resolved, hence closing this issue.
Feel free to raise a new issue or reopen this if you still face it.

Thank you.