0.3 Activation doesn't deal with name collisions

RESOLVED FIXED in 0.3

Status

Cloud Services
General
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: thunder, Assigned: anant)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
I attempted to activate my 0.3 account via services.m.c, but I already had a 'thunder' account with the development box.  So I got this error:

Sorry, your Weave 0.3 account could not be activated because of quota limitations.

It's a mistake, because it did change my cluster.  However, now the accounts are out of sync, because my passwords for services.m.c and the development server are actually different.

I think we should change the services.m.c activation script to catch this case and present an error to the user.  We have a few other accounts, so it could happen again.
(Reporter)

Updated

9 years ago
Blocks: 470634
(Reporter)

Updated

9 years ago
No longer blocks: 470579
(Assignee)

Comment 1

9 years ago
I've updated the script to catch this case. If the username is already in use by the 0.3 server, the activation process will not update the user's primaryNode in LDAP.
Assignee: nobody → anant
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED

Updated

9 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.