Closed Bug 385339 Opened 18 years ago Closed 18 years ago

Camino 1.5 doesn’t work with Bank of America Online Banking

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: huecurve, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.4) Gecko/20070509 Camino/1.5 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.4) Gecko/20070509 Camino/1.5 BofA doesn’t recognize login ID/password when using Camino 1.5. Firefox 2.0.0.4 and Safari work fine. Reproducible: Always Steps to Reproduce: 1. go to <https://onlineid.bankofamerica.com/cgi-bin/sso.login.controller?state=CA> (need an account) 2. enter login info. 3. Site returns invalid login/password info
Does it work with a clean profile <http://pimpmycamino.com/parts/troubleshoot-camino>, or failing that, when spoofing as Firfefox <http://pimpmycamino.com/parts/user-agent>?
Works great using 1.5 here, even though my account wasn't opened in California. No spoofing involved. There are lots of reasons I don't like Bank of America, but they -- and Fleet before them -- worked fine with Camino for everything I've ever done there. Julius -- is this a certain type of banking (i.e., credit card, bank accounts, investment) or does it not work for *anything*? Reason I ask is because Citibank is pretty notorious for not working with Camino on their investment side, but the bank account and credit card sites work fine. I suppose this could be the same situation, although it would be the first report we've had of it at BoA. cl
This is their California Online Banking site. Checking, savings accounts, online bill payments, transfers, etc. After reading this and Stuart Morgan‘s response, I tried logging in again. Worked fine. Don’t know why, although I attempted this multiple times the other day unsuccessfully. Thanks for the feedback. Regards, Julius
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
WORKSFORME, since it wasn't a code change that fixed this. Glad to hear it's working, and thanks for getting back to us!
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.