On Mon, Nov 07, 2011 at 09:31:37AM -0600, Izz Abdullah wrote: > I want to remove them because somehow, they ended up with really odd > permissions which enable them as privileged. I can't see this via the UI, > but it is confirmed when I look at the schema in mysql. So it has been > decided to remove them. I have tried the Shredder and even after doing that, > the user still exists. The old database was duct taped so much I am unsure > of why some things happen the way they do, but they do. I'm just the > cleaner. =) > > -----Original Message----- > From: rt-users-boun...@lists.bestpractical.com > [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Thomas Sibley > Sent: Monday, November 07, 2011 9:25 AM > To: rt-users@lists.bestpractical.com > Subject: Re: [rt-users] Adding users > > On 11/07/2011 09:52 AM, Izz Abdullah wrote: > > I have a question then regarding this. We are at the point now we > > are ready to move our 3.8.6 database to our 4.0.2 installation. I am > > using LDAP authentication in the new install, but it was not being > > used in the 3.8.6 install. At some point in the past, the group here > > imported ALL LDAP users into MySQL so that accounts would already be > > created for them. I had planned to go in and run a sql script I have > > put together to delete all MySQL local users (except for a few in IT, > > and the needed Nobody, RT_System, root, etc.) directly. Can someone > > point me in a 'better' way to do this using the API? These are all > > unprivileged users, and maintaining history correlation for the > > accounts in which I will remove is not an issue (e.g. it is ok that > > old tickets will not have an owner associated with them). > > Why do you want to remove the users? > > If you must, shredder is the way to go and will handle database integrity. > > Thomas
Sounds like you may have issues in your DB related to operating directly on it rather than using the API. Generally speaking, users in RT are never deleted, only disabled. I have an issue myself in that we went through a re-brand, resulting in users mail addresses changing so creating duplicate users. I was going to use the MergeUsers extension to correct this, but last time I checked it hadn't been updated to work with RT4, and I haven't got the spare bandwidth to work on a patch for it atm. Current workaround for the few affected users is to rename and disable the old user, then run a search for the old user's tickets and change requestor/ownership to the new user. -- Richard Clark rich...@fohnet.co.uk
signature.asc
Description: Digital signature
-------- RT Training Sessions (http://bestpractical.com/services/training.html) * Barcelona, Spain November 28 & 29, 2011
