Incorrect Token behaviour while the admin set/unset some settings

[monteshot]

Preconditions and environment

• Magento version - any (with GraphQL solution)
• "Old" users

Steps to reproduce

Precondition:

• Set the Cookie lifetime for a big number(a year - 31536000) - you must have the user session "from the past". I mean, with an old token like "Bearer r1oz2fi2fyqehs89wvbsimndpn16ocay"
• Disable Customer token lifetime
• Go to any checkout solution which works on GraphQL - you get the error. Because in \Magento\Integration\Model\OpaqueToken\Reader::read settings handle incorrectly

Expected result

Error not raises. New tokens not reissued seamlessly

Actual result

Error raised. The new token works as a new

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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[bot]]

Hi @monteshot. 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. :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.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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.

[engcom-Delta]

Hi @monteshot ,

Thanks for your reporting and collaboration. We have verified the issue in Latest 2.4-develop instance & 2.4.8-beta1 instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

1. Set the Cookie lifetime for a big number(a year - 31536000) - you must have the user session "from the past". I mean, with an old token like "Bearer r1oz2fi2fyqehs89wvbsimndpn16ocay"

2. Disable Customer token lifetime

3. Go to any checkout solution which works on GraphQL

4. Observe error is not displaying

Can you please re-verify and confirm if you are still facing the issue. Thanks.

[engcom-Delta]

Hi @monteshot ,

This issue is being closed since it has not been updated in a long time. Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.