Closed Bug 424468 Opened 18 years ago Closed 15 years ago

Changing login information doesn't reset user identities inside engines

Categories

(Cloud Services :: General, defect)

Product:
Cloud Services
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: hello, Unassigned)

Details

After resetting login information, logging out/back in, and syncing to a new server, the user hash written to keys.json is still the old one. Some identity object needs to be refreshed on login change.
Targeting 0.2.
Priority: -- → P1
Target Milestone: 0.1 → 0.2
Blocks: 433899
let's consider pushing this to 0.3
Much of the problem here has been fixed via the ID manager, though I'm not sure about the specific use-case in comment #0.
Given that the biggest problems here are fixed, pushing to 0.3.
No longer blocks: 433899
Target Milestone: 0.2 → 0.3
These bugs need to be triaged, removing 0.3 milestone setting.
Target Milestone: 0.3 → Future
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
Component: General → Needs Triage
Priority: P1 → --
QA Contact: general → needstriage
Component: Needs Triage → General
QA Contact: needstriage → general
I suspect this is long since fixed, we don't have this type of problem at this point.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.