User cannot deactivate their own account
Bug #559518 reported by
Stuart Metcalfe
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Expired
|
Wishlist
|
Unassigned |
Bug Description
When we shared a db with Launchpad, users were able to deactivate their own accounts from the Launchpad UI. This is no longer possible in the SSO app since we split the db. We should add a way to enable this (assuming we want to retain this functionality). It would be useful to understand the rationale behind user-deactivated accounts in Launchpad.
Changed in canonical-identity-provider: | |
status: | New → Confirmed |
tags: | added: proj-openit |
Changed in canonical-identity-provider: | |
status: | Incomplete → Fix Released |
Changed in canonical-identity-provider: | |
status: | Fix Released → Incomplete |
Changed in canonical-identity-provider: | |
status: | Incomplete → Expired |
To post a comment you must log in.
It might also be worth providing a way for users to 'suspend' their own accounts. Suspended accounts aren't recoverable by the user so we should place suitably large warnings all over the place and possibly introduce an extra confirmation step. This would effectively enable a user to lock their own account if it's compromised or 'delete' it if they don't want to use our service any more.