Open Bug 2015409 Opened 2 months ago Updated 3 days ago

customerauth.triangle.com / canadiantire.com - Does not appear logged in with Standard ETP in PBM

Categories

(Web Compatibility :: Privacy: Site Reports, defect, P3)

Desktop
Windows 10

Tracking

(Webcompat Priority:P3, Webcompat Score:4)

Webcompat Priority P3
Webcompat Score 4

People

(Reporter: ctanase, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs][reduce-protection:not-reproducible])

User Story

platform:windows,mac,linux,android
impact:workflow-broken
configuration:common
affects:all
branch:release
user-impact-score:80

Attachments

(1 file)

Environment:
Operating system: Linux/Windows 10
Firefox version: Firefox 147.0/149

Preconditions:

  • Account needed
  • ETP set to Standard in Private Browsing Mode

Steps to reproduce:

  1. Go to https://customerauth.triangle.com/en/sso/triangle-signin.html?gig_ssoToken=us1_tk1.ctuzdEClBeiIbzrFGbadYDd7vLaZba4pBksS2h5IdRQ&gig_refClient=ctr%2Fweb&gig_lang=en&gig_clp=true&gig_sourceURL=https%3A%2F%2Fwww.canadiantire.ca%2Fen.html&gig_QMSession=1e7bf97c2f14eb8b43661093dc0100e3&gig_QMUser=a391d7db90937fba10e7e22f2bac0f7f
  2. Log into your account.
  3. Observe the behavior.

Expected Behavior:
Logs in.

Actual Behavior:
Does not log.

Notes:

  • Reproduces in ETP Strict (Normal mode) and ETP Standard (Private Browsing mode)
  • Reproduces in firefox-nightly, and firefox-release
  • Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/206185

Attached image image.png
Summary: customerauth.triangle.com - Does not appear logged in with Standard ETP in PBM → customerauth.triangle.com / canadiantire.com - Does not appear logged in with Standard ETP in PBM

The severity field is not set for this bug.
:dmehic, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dmehic)

I can reproduce this, it seems like an etp-breakage due to likely being due to how cookie partitioning works. The login flow is through triangle.com, but the page is www.canadiantire.ca. For me (likely) the correct storage permissions were set on the first try where I also had to go through the register flow. Going through the flow again. Starting a new session, I had to go through the login flow again, starting from canadiantire.ca for the login to work.

Blocks: etp-breakage
Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 4
No longer depends on: tp-breakage
Flags: needinfo?(dmehic)
Priority: -- → P3
Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs][reduce-protection:not-reproducible]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: