User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20100504 SeaMonkey/2.0.5 Build Identifier: When I attempt to login to my account at California Oaks State Bank using SeaMonkey with the UA string Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20100504 SeaMonkey/2.0.5 the site always asks me a challenge question although I indicated on the previous login that I was using a private computer and wanted to register the computer. If I spoof Firefox with the UA string Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20100504 SeaMonkey/2.0.5, NOT Firefox/3.6.3 the challenge question is skipped. Reproducible: Always Development of the bank's Web site was outsourced to Fiserv, Inc. The bank's secure site for accessing accounts is outsourced to Fidelity National Information Services. Communication with the bank itself about this problem reveals that no one at the bank understands the issue. Thus, while the bank's site is entered at <https://www.caloaks.com/>, the problem appears at <https://www.gfswebbank.com/pbi_pbi1961/Pbi1961.asp?WCI=MFA&WCE=PasswordSubmit>, www.gfswebbank.com being a domain owned by Fidelity National Information Services. I cannot tell whether Fiserv, Inc. or Fidelity National Information Services is at fault.
I have notified both Fiserv, Inc. and Fidelity National Information Services of this problem.
This bug report has been overcome by events and is no longer valid. California Oaks State Bank was bought out by California United Bank at the beginning of 2011. This past weekend, they finally merged online accounts from California Oaks State Bank into California United Bank's online account system. Today, I was able to login to my account at California United Bank without spoofing Firefox.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
That's make this FIXED, then, by the death of the bank.
Resolution: INVALID → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.