Closed Bug 143904 Opened 22 years ago Closed 22 years ago

citizensbankonline.com - Mozilla won't log in to this OnLine Bank

Categories

(Tech Evangelism Graveyard :: English US, defect)

Product:
Tech Evangelism Graveyard
Component:
English US
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 171331

People

(Reporter: pwinthrop, Assigned: arun)

References

(
URL
)

Details

(Whiteboard: [login required]) 

the web site will not process.

I'm running Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc2) Gecko/20020510 on
Win98
Others appear to be able to log in fine... they just can't stay logged in.  See
bug 142145.  Does that appear to be the issue you're having?
no - I can barely get the actual log in page.  If I do get the log in page, and
put in my username and password, it will keep on spinning but never actually get
into my account.

Hmm, i can't test this because i have no Account.
(i get :  Error #1008 - Invalid user ID.)

-> PSM for triage
Assignee: Matti → ssaux
Component: Browser-General → Client Library
Product: Browser → PSM
QA Contact: imajes-qa → junruh
Version: other → unspecified
I don't see any conclusive evidence that there's something wrong with PSM here.
-> evangelism
Assignee: ssaux → aruner
Component: Client Library → US Banks
Product: PSM → Tech Evangelism
QA Contact: junruh → bclary
Whiteboard: [login required]
The sites certificates seem to have a problem since I receive three instances of:
Error trying to validate certificate from www.citizensbank.com using OSCP -
response contains a date which is in the future.
Summary: Mozilla won't log in to this OnLine Bank → citizensbankonline.com - Mozilla won't log in to this OnLine Bank

*** This bug has been marked as a duplicate of 171331 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Moving to new component
Component: US Banks → English US
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.