Closed Bug 470632 Opened 16 years ago Closed 16 years ago

0.3 Activation doesn't deal with name collisions

Categories

(Cloud Services :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hello, Assigned: anant)

References

Details

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.
Blocks: 470634
No longer blocks: 470579
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
Closed: 16 years ago
Resolution: --- → FIXED
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.