Luma header links do not always reflect authentication status after logging out when using Varnish

[timothyfisherdev]

Preconditions and environment

• Magento: 2.4.5
• Varnish: 7.3.0 (stores -> configuration -> advanced -> system -> full page cache (set to Varnish))
• Install sample data
• Luma theme
• I'm in developer mode so I can see the Varnish headers

Steps to reproduce

1. Visit the storefront home page (in my case https://magento.test).
2. Click the sign-in link in the top right.
3. Sign-in with the sample data customer (roni_cost@example.com / roni_cost3@example.com)
4. After being redirected back to the home page, you'll see the welcome message / dropdown in the top right. Click the dropdown arrow and sign-out.
5. You'll be redirected to the logoutSuccess page (note that the top bar in the header correctly shows the default welcome msg as well as the sign-in/create account links)
6. Once you are redirected to the home page, the top bar makes it look like you're still signed in. It shows the welcome message with a dropdown to view your account, wishlist, and log out. The sign-in/create account links are not visible.
7. Refresh the page to get the top bar to properly show the guest links.

Expected result

When Varnish cache is enabled, the top bar links should still properly reflect whether the customer is logged in/out.

Actual result

You have to refresh the page after the logout redirect to get the top bar links to properly reflect whether you're logged in/out.

Additional information

I've only been able to reproduce this when Varnish is enabled. If I switch the full page cache setting to the built-in cache, everything works as it should.

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.
• [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

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

[timothyfisherdev]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @timothyfisherdev. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @timothyfisherdev, here is your Magento Instance: https://cdf0b9b015a1194edb1f378d65fb2641.instances-prod.magento-community.engineering Admin access: https://cdf0b9b015a1194edb1f378d65fb2641.instances-prod.magento-community.engineering/admin_191c Login: 84346098 Password: 073fd925c784

[timothyfisherdev]

I was able to reproduce this on the provided Magento instance. I switched the configuration setting to Varnish and went through the same steps. I know that Varnish is probably not installed on that demo instance, but, just switching the setting to Varnish seems to be enough to reproduce the issue.

After being redirected from the logoutSuccess page:

[m2-assistant[bot]]

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

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

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://cdf0b9b015a1194edb1f378d65fb2641.instances-prod.magento-community.engineering Admin access: https://cdf0b9b015a1194edb1f378d65fb2641.instances-prod.magento-community.engineering/admin_114d Login: 46168130 Password: 47d60efba421

[engcom-Bravo]

Hi @timothyfisherdev,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Visit the storefront home page (in my case https://magento.test/).
• Click the sign-in link in the top right.
• Sign-in with the sample data customer (roni_cost@example.com / roni_cost3@example.com)
• After being redirected back to the home page, you'll see the welcome message / dropdown in the top right. Click the dropdown arrow and sign-out.
• You'll be redirected to the logoutSuccess page (note that the top bar in the header correctly shows the default welcome msg as well as the sign-in/create account links)
• Once you are redirected to the home page, the top bar makes it look like you're still signed in. It shows the welcome message with a dropdown to view your account, wishlist, and log out. The sign-in/create account links are not visible.
• Refresh the page to get the top bar to properly show the guest links.

The top bar links not reflecting properly whether the customer is logged in/out.

Hence confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-8552 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.