Hi Peter,
On Jun 4, 2010, at 7:25 AM, Pieter Neerincx wrote:
Dear Greg,
On Jun 3, 2010, at 2:51 PM, Greg Von Kuster wrote:
> Hello Peter,
>
> You'll need to uncomment the following lines in the ~/lib/galaxy/admin.py
controller (lines 92-94 in the latest rev):
>
> #operations.append( grids.GridOperation( "Delete", condition=( lambda
item: not item.deleted ), allow_multiple=True ) )
> #operations.append( grids.GridOperation( "Undelete", condition=( lambda
item: item.deleted and not item.purged ), allow_multiple=True ) )
> #operations.append( grids.GridOperation( "Purge", condition=( lambda
item: item.deleted and not item.purged ), allow_multiple=True ) )
>
> The buttons will then be displayed on the manage users page in the admin view. Be
aware that "deleting a user" only marks the user as deleted ( the deleted column
is True ) in the database, keeping the state of everything associated with the user,
allowing for undeletion if desired.
Thanks for the info! Is there any particular reason why this is disabled by default?
This is disabled by default because:
- it is very rarely needed ( if ever ), and probably should never be used in production
instances
- We have a TODO item in the code to add an enhancement to be able to check the
configuration setting before displaying the buttons, but it is low on the priority list
for now ( again, because this feature is questionable in production instances ).
I know Galaxy's philosophy is to save everything you do to make
sure research is reproducible, but sometimes it can be really handy to delete stuff. I was
trying to debug an issue with user account registration forms and therefore created dozens
of accounts to see if the issue was gone after fiddling with my Galaxy and Apache configs.
And I really really want to delete those phony test accounts as they clutter up the lists
for sharing histories and workflows with colleagues :).
If debugging, it may be better to use a Galaxy instance that is not your production
instance where the database can easily be dropped and recreated as necessary.
> If you want to go further, you can "Purge the user" after you have deleted
their account. Here is what happens when you purge the user's account:
>
> # This method should only be called for a User that has previously been
deleted.
> # We keep the User in the database ( marked as purged ), and stuff associated
> # with the user's private role in case we want the ability to unpurge the
user
> # some time in the future.
> # Purging a deleted User deletes all of the following:
> # - History where user_id = User.id
> # - HistoryDatasetAssociation where history_id = History.id
> # - Dataset where HistoryDatasetAssociation.dataset_id = Dataset.id
> # - UserGroupAssociation where user_id == User.id
> # - UserRoleAssociation where user_id == User.id EXCEPT FOR THE PRIVATE ROLE
> # Purging Histories and Datasets must be handled via the cleanup_datasets.py
script
>
> Again, the user's record remains in the database, but you can manually remove it
and the private role using sql if you wish ( we do not advise this, but it's not hard
to do). The user's private role is in the role table where the type is private and
the name is the user's account / email address.
To reduce the amount of manual maintenance work on a Galaxy install it would be nice if
functionality for purging users would eventually be added to the cleanup scripts just like
for the datasets and histories...
We'll consider this ( e.g., if a user has been deleted for X number of days, they can
be purged ). However, this will probably be fairly low on the priority list as well.
Thanks,
Pi
> On Jun 3, 2010, at 6:04 AM, Pieter Neerincx wrote:
>
>> Hi,
>>
>> In my univers_wsgi.ini I have:
>>
>> # Can an admin user delete user accounts?
>> allow_user_deletion = True
>>
>> But when I go the the admin web interface -> security -> manage users, I
cannot delete users. There is only a "Create New User" button at the top and a
"for selected users: Reset Password" button at the bottom... Am I missing
something?
>>
>> Cheers,
>>
>> Pi
>>
>>
>> ---------------------------------------------------------------
>> Biomolecular Mass Spectrometry & Proteomics group
>> Utrecht University
>>
>> Visiting address:
>> H.R. Kruyt building room O607
>> Padualaan 8
>> 3584 CH Utrecht
>> The Netherlands
>>
>> Mail address:
>> P.O. box 80.082
>> 3508 TB Utrecht
>> The Netherlands
>>
>> phone: +31 6 143 66 783
>> email: pieter.neerincx(a)gmail.com
>> skype: pieter.online
>> ---------------------------------------------------------------
>>
>>
>> _______________________________________________
>> galaxy-user mailing list
>> galaxy-user(a)lists.bx.psu.edu
>>
http://lists.bx.psu.edu/listinfo/galaxy-user
>
> Greg Von Kuster
> Galaxy Development Team
> greg(a)bx.psu.edu
>
>
>
-------------------------------------------------------------
mobile: +31 6 143 66 783
e-mail: pieter.neerincx(a)gmail.com
skype: pieter.online
-------------------------------------------------------------
_______________________________________________
galaxy-user mailing list
galaxy-user(a)lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-user
Greg Von Kuster
Galaxy Development Team
greg(a)bx.psu.edu