Chase Bank site - blocking access via SeaMonkey

[Peter Creasey]

Working here, business account, https://chaseonline.chase.com/Logon.aspx.

t, doesn't work for me. I log in and immediately am advised to upgrade my browser to non-SM selections.

[rsx11m]

I'd suggest to keep complaining to Chase - sufficient noise may make them reconsider their absolute stance.

I keep the Firefox/43.0 token disabled on purpose, thus I'm running into quite a few sites not recognizing SeaMonkey correctly. But, many of those will just present a notification and then you can go on (occasionally acting funny with some default/generic JavaScript being served). Those banking sites are annoyingly aggressive with respect to the "supported" browsers, maybe their legal team asks for that to avoid issues with a malfunctioning site (transactions going wrong, etc.). But anyway, no reason not to do it right!

[Myhrddin]

Working here, business account, https://chaseonline.chase.com/Logon.aspx.

t, doesn't work for me. I log in and immediately am advised to upgrade my browser to non-SM selections.

Please, make them aware of your dissatisfaction with their new site then.
Only when they hear enough is anything likely to change.

[Myhrddin]

Just so it's posted.. This is the link I use.

https://chaseonline.chase.com/Logon.aspx

Which allows me into the checking account but, boots me out to browser choice when using my credit login.

[Myhrddin]

Yeah, they screwed something up with their website - see https://bugzilla.mozilla.org/show_bug.cgi?id=1277111 and related https://bugzilla.mozilla.org/show_bug.cgi?id=1230783

It was discussed before:
http://forums.mozillazine.org/viewtopic ... #p13948475
http://forums.mozillazine.org/viewtopic ... #p14057585

@mpdooley
Two things:
1) User Agent must be changed:
Add name "general.useragent.override.chase.com" with value "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko". Since then SeaMonkey will have fake Internet Explorer user agent but for chase.com site only.
2) Chase.com request "referer":
"network.http.sendRefererHeader" must be set to default "2".

As a customer write to the Bank and request better service.

THANKS.! THAT WORKED :: No Worries though, I have given them an earful already .. and done posts on Twitter, Google+ & Facebook (even though I don't regularly use them). Figure every little bit helps.

[Peter Creasey]

I can't get past the change browser popup to submit a complaint.

[Anonymosity]

Give them a nice fake user-agent that does not contain the word "SeaMonkey".

[rsx11m]

Since they claim it's working with Firefox, I'd try its current UA:

• Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0

[Myhrddin]

I've been using the changes mentioned below to access my Chase account. But, I am not letting them off the hook just because I can fool 'em into accepting my login. Today, they asked me to do a survey. *chuckling -- Oh, I did the survey alright. I didn't give them awful scores on everything.. mainly neutral scores but, made sure to let them know that I was very unhappy, as are other SeaMonkey users who are Chase customers, that there is no effective way to make Chase (or their coders) aware of this issue.. and that we're not pleased to have to trick them into letting us in via their New Site but, they've given us little choice.
We have heard nothing back (which to my knowledge is true) and no real way to get word to the people who could actually do anything about it.
If you're still waiting for them to fix this, I suggest you make the changes outlined below by @mpdooley and get logged in.
Then, maybe you'll be asked to do a survey too. Plus, once you're in, you have a better opportunity to give them feedback as well.

Thanks guys. Let's not give up. This is something that really should be straightened out. And, if we can get the right people's attention at Chase, I think they'll make sure it gets done.

-Myr
.end.trans.

Yeah, they screwed something up with their website - see https://bugzilla.mozilla.org/show_bug.cgi?id=1277111 and related https://bugzilla.mozilla.org/show_bug.cgi?id=1230783

It was discussed before:
http://forums.mozillazine.org/viewtopic ... #p13948475
http://forums.mozillazine.org/viewtopic ... #p14057585

@mpdooley
Two things:
1) User Agent must be changed:
Add name "general.useragent.override.chase.com" with value "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko". Since then SeaMonkey will have fake Internet Explorer user agent but for chase.com site only.
2) Chase.com request "referer":
"network.http.sendRefererHeader" must be set to default "2".

As a customer write to the Bank and request better service.

[Myhrddin]

I can't get past the change browser popup to submit a complaint.

If you have a Twitter.com account, they have a support outlet there at;
https://twitter.com/ChaseSupport

That's one way you can get word to them about your difficulties logging in.

[mpdooley]

Since they claim it's working with Firefox, I'd try its current UA:

• Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0

Thanks......that finally worked.

I tried several variants of user agents I had on my system but these apparently were too old or had other issues.

Today tried a followup and Used User agent Switcher Version 0.7.3
http://chrispederick.com/work/user-agent-switcher/
NOTE: My Version may be something rebuilt for SeaMonkey

Then created a User Profile as follows:
08/24/2016 12:12 PM - Chase Bank Access:
Used User Agent Switcher and created a profile for Firefox 47 using:
Description: Firefox 47.0
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
App Code Name: Mozilla
App Name: Netscape
App Version: 5.0 (Windows)
Platform: Win32

Now then - this works for me and using a windows 7 Professional 64-bit system. Likely the Key is simply the User Agent Description.

Still, someone might be able to better list what the correct "other settings" should be for this Version of Firefox.

I am currently using SeaMonkey 2.39 but my recollection is that I had the same issues on other systems even when updating to SM 2.40.

As such I can currently get into Chase using:
Avast SafeZone Browser - Version 1.48 - Version: 1.48.2066.95
Internet Explorer - Version 11.0.9600.18097

and now......by using this "tricked up" version of SeaMonkey.

THX