Can not login to wellsfargo.com

[guido99]

Eloston/ungoogled-chrome
Google-Chrome

Release 100.0.4836.127

Cannot login to wellsfargo.com

Enter username, password, & click submit button. Screen redraws. The username & password fields are cleared prompting for input again. No error messages. Perusal of the chrome_debug.log after starting with command line options --enable-logging --v=1 shows no obvious issue (novice speaking here).

Normal expected mode. Fill login data & click submit leads to 2factor-verification prompt screen.

Observed on Lenovo P15 with Fedora 35, Slackware linux 15.0 (separate partitions) and on a Lenovo X390 running Fedora 36 in Gnome 42 GUI. With this same hardware, Firefox 91.8 & 99.0 function flawlessly; Fedora 35 Chromium 93.0.4577.63 also behaves properly.

Curiously, no problem on my Motorola Android cell phone using this release!

All earlier releases prior to 100...127 worked fine.

[guido99]

Error: I meant rel 100.0.4896.127.

[networkException]

Note: It is very difficult to debug a problem on websites that require authorization, a payed subscription or similar, as its unlikely that a ungoogled-chromium maintainer has access to the service as well.

Can you check that vanilla chromium with the same version on the same system that you are experiencing the error on does not have the issue as well?

[tomasz1986]

From my experience, these kind of problems are usually caused by blocking of 3rd party cookies, which Ungoogled Chromium does by default, while vanilla Chromium does not.

Compare the default settings in Ungoogled Chromium:

versus the default settings in vanilla Chromium:

Vanilla Chromium blocks 3rd party cookies in Incognito only, while Ungoogled Chromium does it universally. I've experienced problems with being unable to log in myself, e.g. on banking or shopping sites, and the only solution was to allow all cookies.

[guido99]

"Vanilla Chromium blocks 3rd party cookies ..."

I always use Allow all cookies.

I have "fiddled" with numerous security & privacy site-settings; nothing works!

[guido99]

"Note: It is very difficult to debug a problem on websites that require authorization..."

I'm well aware of that. WFB is a big bank. Maybe a GitHub developer has an account.

"Can you check that vanilla chromium with the same version on the same system that you are experiencing the error on does not have the issue as well?"

The fault appears on vanilla chromium of same rel. Anything earlier is OK. This just appeared when 127 was available.

[PF4Public]

It could be helpful to investigate the Developer console.

[guido99]

After failing login, this is screenshot from developer tools. dectector-dom-min.js. Something is not being authenticated.

[PF4Public]

Look into "Console". There might be some errors.

[guido99]

Console output. Click on sources gives screenshot I show previously.

[guido99]

More data of same as above on 4 issues.

[guido99]

Logged on to troubled URL with firefox. Disabled 2 factor auth. Logged in with ungoogled-chrome! Activated 2 factor auth. Tested. All is well! Why? (We'll likely never know.)