Unable to access Commerzbank bank account
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(firefox-esr91 unaffected, firefox100 fixed, firefox101 fixed, firefox102 fixed)
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox100 | --- | fixed |
firefox101 | --- | fixed |
firefox102 | --- | fixed |
People
(Reporter: flod, Assigned: denschub)
References
Details
(Keywords: webcompat:site-wait)
With Firefox, after providing username and password, you get a "Technical error page" and the login fails. Normally, it would display a page while it waits for you to confirm the login with your photoTAN application.
The login was broken on Nightly for a while for me, but now even release doesn't work (Firefox 100). Not sure if this can be tracked down to a feature that was enabled by default in 100?
The profile is pretty clean (no add-ons), tried also with Tracking Protection disabled. Nothing useful in the console either.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Did you toggle ETP off via the toggle in the protections panel (shield icon)? And if you do that, does the issue still occur?
Reporter | ||
Comment 3•3 years ago
|
||
(In reply to Paul Zühlcke [:pbz] from comment #2)
Did you toggle ETP off via the toggle in the protections panel (shield icon)?
Correct, and that doesn't fix the error.
Aryx is seeing the same thing, and trying to bisect. Are you aware of any default setting that changed from 99 to 100?
Comment 4•3 years ago
|
||
OK, so it's probably not anti-tracking related then. I unfortunately don't have a Commerzbank login so I can't test.
![]() |
||
Comment 5•3 years ago
|
||
This breaks if version 100 is used in the useragent. If one sets the preference general.useragent.override
to Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0
, the login succeeds.
Reporter | ||
Comment 6•3 years ago
|
||
Maybe easier for folks affected: set network.http.useragent.forceVersion
to 99 (default should be 0). Needs a browser restart to take effect.
Assignee | ||
Comment 7•3 years ago
|
||
This is User Agent sniffing. We can ship a WebCompat Intervention here to cap the UA to Version 99, until they have a chance to fix. Most likely, this is important enough for an out-of-band update.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 8•3 years ago
|
||
We're rolling out a System Addon Update (see bug 1767811) that addresses this issue for Release users. The same intervention is also shipping in Nightly. Uplift into Beta is pending.
Updated•3 years ago
|
Assignee | ||
Comment 9•3 years ago
|
||
We have shipped a User Agent override, which is available in all channels. This is still a valid issue that should remain open as we're still waiting for them to react, but since this needs no immediate action from the WebCompat team, I'll drop the priority for now.
Comment 10•2 years ago
•
|
||
Francesco, could you please test this issue with a clean profile on the latest Firefox Nightly with the following settings in "about:config"?
"about:config" settings:
extensions.webcompat.perform_ua_overrides false
extensions.webcompat.perform_injections false
Reporter | ||
Comment 11•2 years ago
|
||
It seems to be working now (Firefox 110.0a1, Build ID 20230112093539)
Updated•2 years ago
|
Description
•