Re-activated users should also get their name restored.

Bug #499459 reported by Henning Eggers
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Currently, if a user de-activates his/her account and later activates it again, the account name keeps the "-deactivatedaccount" suffix. This would look much better and be less confusing if the original name was restored upon re-activation, if possible.

Gary Poster (gary)
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
affects: launchpad-foundations → launchpad-registry
Revision history for this message
Curtis Hovey (sinzui) wrote :

Person.reactivate() does fix the user name. I think the path for reactiving users has changed because user forgot password would ensure this was called LoginToken.reactivate().

Curtis Hovey (sinzui)
affects: launchpad-registry → launchpad-foundations
Revision history for this message
Selene ToyKeeper (toykeeper) wrote :

I don't think this is working... I occasionally get delete-account requests from people with usernames like this:
https://launchpad.net/~cic-aster-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount

Revision history for this message
Curtis Hovey (sinzui) wrote :

Login via SSO (which is the only way to login now) probably does not use reactivate().
/me looks
Oh, Nothing calls it now that SSO is used. So while Lp has a method to ensure reactivation is sane, nothing ever calls it.

Revision history for this message
William Grant (wgrant) wrote :

This relates to the reactivation and other account management workflows that I speculate on in https://bugs.launchpad.net/canonical-identity-provider/+bug/556680/comments/5

Revision history for this message
William Grant (wgrant) wrote :

            elif person.account.status in [AccountStatus.DEACTIVATED,
                                           AccountStatus.NOACCOUNT]:
                removeSecurityProxy(person.account).reactivate(comment)
                removeSecurityProxy(person).setPreferredEmail(email)

It seems like those two rSP lines could just be replaced with removeSecurityProxy(person).reactivate(comment, email).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.