Comprehensive 'remove user' functionality
Description
incorporates
Activity
Aaron Zeckoski March 27, 2012 at 12:35 PM
CLE team bulk inactive issues cleanup - if this is important then reopen or create a new issue
David Horwitz February 23, 2010 at 6:33 AM
MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly
Former user August 21, 2008 at 5:07 AM
Any update on this? User traces still remain which cannot be removed (except for going to SQL)
Peter Knoop January 12, 2006 at 10:06 AM
Related to this, but perhaps a separate issue, is what to do with users' artifacts from tools that are removed from a site. Should there be a difference between deleting a tool form a site and removing it (hiding the tool and its content)? Should artiifacts be completely deleted when a tool is deleted or removed? Should artifacts be hidden, but if the tool is re-added, then the previous content is still there? (Gives an easy way to recover from accidently removing a tool.) Should artifacts be hidden, but if the tool is re-added, then a choice presented for starting fresh or restoring previous content? (Gives an easy way to clean out a tool, such as when new instructors explore their site by creating junk content when they are getting used to Sakai or starting a new term.)
Details
Priority
MajorAssignee
UnassignedUnassignedReporter
Stephen MarquardStephen Marquard
Details
Details
Priority
Major
There is a need for a more comprehensive "remove user" fucntionality than currently exists. One that not only deletes the user, but all the appropriate, associated data, such as their MyWorkspace site, their memberships, etc., rather than leaving it orphaned in the db. Note that for some cases, such as users from external providers, it may not be desireable to delete all the related artifacts when deleting the internal user representation in Sakai, so support should be provided for both the current and the proposed delete user functionality. This likely to be a larger problem in projects than in course sites, where users from outside the orginization are likely to be using guest accounts.
Use Cases:
Deleting a user and all their associated material
Deleting just the Sakai, internal user account, but not their associated material
---------------------------------------- Original Description:
When a user is deleted through the GUI (Users tool, 'Remove user'), not all artefacts and associations of the user are removed. For example, the user's my workspace site remains, as does realm membership or any sites of which the user was a member.
In some cases, this behaviour is desirable (for example where a user was created internally but also exists through a provider), whereas in other cases it is undesirable, leaves behind orphaned data in the db and/or may have security implications (OOTB configurations and configurations where userids of internal users may not be unique across the lifespan of the application, e.g. guest accounts where the email address is the userid).
The issues are described further in these JIRA items:
http://bugs.sakaiproject.org/jira/browse/SAK-655
http://bugs.sakaiproject.org/jira/browse/SAK-1535
http://bugs.sakaiproject.org/jira/browse/SAK-1456
http://bugs.sakaiproject.org/jira/browse/SAK-2973
A more comprehensive 'remove user' capability is required (whether invoked via the GUI, web services or API), which is flexible or configurable enough to cope with various deployment scenarios, i.e. ways in which the Sakai internal user db and external providers interact.