Closed
Bug 507975
Opened 17 years ago
Closed 16 years ago
Sign in fails after updating to 0.5
Categories
(Mozilla Labs :: Identity, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: alfonso.mingo, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)
Build Identifier: Weave 0.5
After updating Weave to 0.5 i cannot sign in anymore, i have not changed anything in my credentials but i receive the following message every time i try logging in:
"Invalid username, password or passphrase"
Reproducible: Always
Steps to Reproduce:
1.upgrade an older release to 0.5
2.try signing in
3.
Actual Results:
the sign in interface shows the error message: "Invalid username, password or passphrase"
Expected Results:
sign in successful
i made no changes to my username/password or passphrase prior or after upgrading to 0.5
Comment 1•16 years ago
|
||
Did you ever get error messages in your activity log prior to upgrading to 0.5? Errors like "unwrapSymmetricKey"?
Somehow the passphrase that you've been using isn't the one that can decrypt the data stored on the server.. ?
I have never seen anything like that.
I did try retyping the passphrase and at some point it worked, but i am sure i never altered it myself prior to the error, i keep it in a password manager, i used its stored content to enable another pc without any problems, although i did not upgrade weave on that.
Comment 3•16 years ago
|
||
I had an early account as well, I can't sign at all now.
I can reset my password, I can reset my passphrase, but signing in always fails.
Comment 4•16 years ago
|
||
Weave 0.6 will let you know if user/pass is wrong or passphrase is wrong. If you still get a passphrase issue, multiple machines might be using different passphrases.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Updated•15 years ago
|
Product: Mozilla Services → Mozilla Labs
Target Milestone: --- → --
You need to log in
before you can comment on or make changes to this bug.
Description
•