Solved Citibank (USA) no longer reliably works with Vivaldi

redbike

Before 6 April 2022 (on which day, coincidentally, I upgraded to Vivaldi v5.2.2623.24) I could reliably log onto Citibank (USA):

https://online.citi.com/US/JPS/portal/Home.do?jfp.layout=Full

On 6 April 2022 (and since), this page was sometimes displayed rather than the log-in page:

https://online.citi.com/US/CBOL/pnt/activity/flow.action

Worth noting: this page is dated (at the bottom) Aug 1, 2017. Bleakly amusing: Internet Explorer is supported while Vivaldi isn't. Onward.

Sometimes, the Citibank log-in page displays; sometimes not. Further, after successfully logging in, some internal Citibank pages are now randomly replaced with the 'update browser' page.

I truncated the Citibank URL to https://online.citi.com/ which seems to more reliably present the login page. The 'update browser' page still sometimes appears either in place of the log-in page or internal pages within the Citibank site.

I have only one extension (Ublock Origin) installed.

Back in the Olden Days, some browsers included a setting / option to allow emulating other browsers and sometimes that resolved issues like this. Sniffing around Vivaldi's Tools and Settings, I didn't find this option. Is it available?

Adding: I haven't complained to Citibank. Frankly / bluntly: they couldn't give a damn. Presumably / hopefully, Vivaldi does.

Pathduck

@redbike Hello and Welcome to the Vivaldi Community

Kind of knew we'd see some issues about this - actually surprised we've not seen more of them, I'm guessing more will come.
https://www.theverge.com/2022/2/17/22938721/chrome-firefox-edge-version-100-websites-bug-compatibility-issues-mozilla-google-microsoft
https://www.techradar.com/news/chrome-100-could-break-your-website-but-google-is-on-it

It's not like the sites haven't had plenty of time to plan for this... it's like Y2K all over again

FYI - I get the same "Upgrade your browser" in Chrome and Chromium v.100. I used developer tools to change the UA string to "Chrome/99.0.4896.81" and it started working

I'm assuming the Citibank people will be very much aware of this by now and probably getting a lot of reports. Probably some poor IT folk sweating buckets over there...

For your issue - no good workaround exists before the site gets their stuff together. You could use a UA switcher extension temporarily, like this one:
https://chrome.google.com/webstore/detail/user-agent-switcher/kchfmpdcejfkipopnolndinkeoipnoia/
Not too difficult to set up, I can help out.

I suggest you also contact your bank about this, as it's not a Vivaldi-specific issue.

redbike

@pathduck

I tried, with limited success, to edit the Vivaldi UA string. Limited success: my edit only appeared on the edited 'About' page. It was neither saved nor was it universal.

I installed the user-agent-switcher extension you suggested. Let's just say: its use isn't intuitive. Despite the extension's best efforts, I think I'm now identifying my installation of Vivaldi to citi.com as Chrome/99.0.4896.81 as you advised.

Probably some poor IT folk sweating buckets over there...

Not a chance. Further, I expect Google/Chrome/Chromium regards this as a feature.

Bottom line: I can't see either Citi or Google/Chrome/Chromium considering this to be a problem, certainly not theirs. If it's to be resolved, it'll be by Vivaldi (and other non-supported browsers).

Time will tell whether use of the user-agent-switcher extension actually resolves this. I'll add (related to the extension): both Ars Technica and Krebs on Security report regularly on 'When Good Extensions Go Bad'. I try to minimize their use.

Pathduck

@redbike said in Citibank (USA) no longer reliably works with Vivaldi:

I installed the user-agent-switcher extension you suggested. Let's just say: its use isn't intuitive. Despite the extension's best efforts, I think I'm now identifying my installation of Vivaldi to citi.com as Chrome/99.0.4896.81 as you advised.

You can check your UA string on for instance:
https://www.whatismybrowser.com/detect/what-is-my-user-agent/

I didn't quite understand from your post if it's working as expected or not with the extension?

There is a way to map a UA string definition to only activate on a single site/domain, and that's what I suggest you do. Look in the extension setting "Permanent Spoof List".

redbike

I didn't quite understand from your post if it's working as expected or not with the extension?

Sorry for my lack of clarity. The problem was intermittent. I installed the user-agent-switcher extension and entered citi.com on the "Permanent Spoof List". Thanks for confirming this was the appropriate action.

Yes, I can now visit citi without getting the error page, but only time will tell if this is a permanent fix.

I'll follow up — sooner if the problem recurs, but I think it's prudent to allow at least a week to consider this resolved.

Pathduck

@redbike Thanks for clarifying, and good it seems to be working for you now

What I suggest you do now is keep the extension, but once in a while disable it to check if the site has improved its UA detection. Maybe test once a week or so. Or, depending on how often you use the site, just enable it when doing banking.

After that you can just keep it permanently disabled or remove it. I always keep a UA changer extension around, but only enable it for testing stuff like this.

The Chromium 100 releases are just a couple days old now, so hopefully it will be sorted out in at least a couple weeks.