1804225 - Unable to login on samsung.com with Standard ETP

Status: RESOLVED WORKSFORME

(Core :: Privacy: Anti-Tracking, defect, P3)

Description

[Calin Tanase]

Attachment: samsung.png

Environment:
Operating system: OnePlus 6 A6000 (Android 11) / Google Pixel 5 (Android 13)
Firefox version: Nightly 109.0a1-20221205093546 / Release 107.0.1-20221128144904

Preconditions:
• ETP set to Standard
• Clean profile

Steps to reproduce:

1. Go to https://www.samsung.com
2. Try to login into your account. (regular, not through google)
3. Observe the behaviour.

Expected Behaviour:
The login is performed succesfully.

Actual Behaviour:
An error message is displayed the login is not performed.

Notes:

1. Reproducible on both Firefox Release and Nightly (Standard and Strict ETP)
2. Not reproducible with ETP OFF
3. Same behaviour in Private

Comment 1

[Tim Huang[:timhuang]]

I can log in successfully with ETP standard on both release and Nightly. Could this be a temporary site issue?

Calin, would you be able to test it again? Thanks.

Comment 2

[Calin Tanase]

Updated my Nightly but I'm still reproducing this issue: https://prnt.sc/vTrU1TZdM2GR

Same with VPN pointing to US: https://prnt.sc/8SSqgKTggH6L

Comment 3

[Tim Huang[:timhuang]]

Thanks, Calin. The error code is 408, it's a Request Timeout. Did you experience any unexpected network issues when doing the test, such as a long delay when doing the login?

Comment 4

[Calin Tanase]

No, it happens instantly. My colleague was able to reproduce it as well.

More issues about login coming on webcompat: https://github.com/webcompat/web-bugs/issues/115143

Comment 5

[Tim Huang[:timhuang]]

I tried to reproduce the issue on an android Nightly, but I still could not reproduce the issue. I can successfully log in, and there was no error code shown.

Comment 6

[Thomas Wisniewski [:twisniewski]]

We just received a report on webcompat.com that a user cannot log in with Google on Samsung's site as well in Standard ETP (https://webcompat.com/issues/121012)

Comment 7

[Harshit Sohaney [:hsohaney]]

I have tried reproducing this issue but could not succeed - I was able to login without any problems. To note, I was sent to a two step verification, I'm not sure if that makes a difference.

Device

• Samsung Galaxy S21+ 5G
• Android 13, One UI 5.1
• Firefox Nightly 116.0a1

Comment 8

[Thomas Wisniewski [:twisniewski]]

The user did specify they were logging in with Google, is that what you tried?

Comment 9

[Tim Huang[:timhuang]]

Calin,

Would you be able to verify this bug again? The problem seems to be not reliably reproducible according to comment 7.

Comment 10

[Calin Tanase]

Tested with Strict ETP with both regular and google login and I'm not longer reproducing this issue.

Environment:
Operating system: Google Pixel 5 (Android 13)
Firefox version: Nightly 116.0a1-20230627094831

Comment 11

[Tim Huang[:timhuang]]

The issue was originally reported for ETP standard mode. Would you be able to verify if it works in ETP standard? Thanks.

Comment 12

[Calin Tanase]

Same behaviour with Standard ETP.

Environment:
Operating system: Google Pixel 5 (Android 13)
Firefox version: Nightly 116.0a1-20230627094831

Comment 13

[Tim Huang[:timhuang]]

Per comment 10 and comment 12, close this bug for now.