Closed
Bug 563932
Opened 14 years ago
Closed 14 years ago
On stage - Login failed: error.login.reason.password No traceback available
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tracy, Assigned: telliott)
Details
Attachments
(1 file)
4.02 KB,
text/plain
|
Details |
Seen with 1.3b4 against https://stage-auth.services.mozilla.com/ Account creation went fine, but doesn't connect. Subsequent attempts to connect also fail. log attached
Flags: blocking-weave1.3?
Reporter | ||
Comment 1•14 years ago
|
||
The [!] alert in the status bar is reporting: Weave encountered an error while connecting: Incorrect username or password. Please try again. The account manager in preferences also reports in red: Incorrect username or password Current user is correct and passwords stored in pwdmngr are correct.
Comment 2•14 years ago
|
||
Right, so this is the "it's broken" that I've been talking about on the weave-all list. I guess I never filed a bug for it. This is down to the mismatch between the sync and reg servers, and the LDAP ACLs.
Comment 3•14 years ago
|
||
This should be fixed. All the python tests are passing against the staging cluster now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•14 years ago
|
||
Verified with 1.3b4 against the staging server.
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Flags: blocking-weave1.3?
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•