On stage - Login failed: error.login.reason.password No traceback available

VERIFIED FIXED

Status

Cloud Services
Server: Sync
--
blocker
VERIFIED FIXED
8 years ago
8 years ago

People

(Reporter: tracy, Assigned: telliott)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
Created attachment 443619 [details]
log of account setup and initial attempt to log-in

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

8 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.
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.
This should be fixed. All the python tests are passing against the staging cluster now.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

8 years ago
Verified with 1.3b4 against the staging server.
Status: RESOLVED → VERIFIED

Updated

8 years ago
Flags: blocking-weave1.3?
You need to log in before you can comment on or make changes to this bug.