Closed Bug 421554 Opened 16 years ago Closed 16 years ago

Previously stored--but now incorrect--submitted login can't be replaced

Categories

(Toolkit :: Password Manager, defect)

x86
macOS
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 419081

People

(Reporter: stephend, Unassigned)

Details

Build ID: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4

Summary: Previously stored--but now incorrect--submitted login can't be replaced

Steps to Reproduce:

1. Have a pre-existing login to a website stored
2. Load the page again, and hit "OK" when prompted to login (the user/pass will be pre-filled)
3. When auth fails, and you're prompted again, enter the correct credentials, and hit OK

Expected Results:

User is able to log in to the site.

Actual Results:

Login fails, and the following exception is thrown:

Error: [Exception... "'This login already exists.' when calling method: [nsILoginManager::addLogin]"  nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)"  location: "JS frame :: file:///Applications/Firefox.app/Contents/MacOS/components/nsLoginManagerPrompter.js :: anonymous :: line 586"  data: no]
Source File: file:///Applications/Firefox.app/Contents/MacOS/components/nsLoginManagerPrompter.js
Line: 586
Flags: in-litmus?
> Steps to Reproduce:
> 
> 1. Have a pre-existing login to a website stored

It's crucial that this login no longer be valid (should be obvious, but clarity++)
in-litmus+

https://litmus.mozilla.org/show_test.cgi?id=5199

juanb!  Please review at your earliest convenience :-)
Flags: in-litmus? → in-litmus+
Is this for HTTP auth, or filling in a form?

When entering the "correct" credentials, exactly what is being changed? Username? Password? Both?
HTTPS over LDAP (internal staging server).

And, both username and password, yes.
Er, LDAP over HTTPS (been a long day).
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
thx, dolske; I can haz duplicate?
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.