Cannot use login as customer in multisites installations if I open the homepage first

[ioweb-gr]

Preconditions and environment

• 2.4.6-p8

Steps to reproduce

Steps to Replicate the Bug in Magento 2:

1. Set up two websites in Magento 2:

   • Web1: Configure this website under the primary domain. For example, https://primary-domain.com.
   • Web2: Configure this website under a different domain. For example, https://different-domain.com.

2. Create a customer in Web2:

   • Log in to the admin panel.
   • Navigate to Customers > All Customers.
   • Click Add New Customer and ensure the customer is assigned to Web2.

3. Test scenario using the same browser session:

   • Open the admin panel (https://primary-domain.com/admin) and log in as an admin.
   • Open a new tab in the same browser session and navigate to the frontend of Web1 (https://primary-domain.com).

4. Attempt to log in as the customer in Web2 via the backend:

   • In the admin panel, go to Customers > All Customers.
   • Locate the customer created in Web2 and click Login as Customer.
   • Observe the behavior in the frontend of Web1.

Possible Cause:

Magento's session management and customer login mechanisms may conflict due to cross-domain cookies, domain-specific sessions, or scope mismatches between Web1 and Web2.

Expected result

The customer should be logged in successfully in Web2.

Actual result

The customer login fails on the frontend of Web1.

Additional information

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 @ioweb-gr. 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.

[engcom-Bravo]

Hi @ioweb-gr,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots.

The customer was able to logged in successfully in Web2.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[ioweb-gr]

I believe the issue is that you're using the same domain for the website. Please use different websites with different root domains , not even subdomains.

e.g.

example.com
example.co.uk