Inserting a user with mysql INSERT

I need to create an account for a catch-all email address that will be sending requests to our RT from a separate workflow. No matter which user triggers the action, the email will appear to come from product.suport@company.com.

When I try to use the GUI to create the user, it fails…looking at the log file, it seems to be because it can’t find an equivalent user in our company-wide Active Directory. (This is a useful thing to seed most user details…name, department, phone, etc. for real people.)

I don’t need all the details for this user, so I decided I’d be OK to have the user created without all the extra goodies, and went right to the mysql command line.

insert into Users set Name=‘productsupport’, EmailAddress=‘product.support@company.com’;

This succeeded fine…I can see the row is in the database. But when I try to call up the user from the admin GUI, it says it can’t find it. Are there other fields I should fill in? Are there actually other tables that need rows inserted too?
Kendric Beachey

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.

The crickets and I poked around in other tables, trying to figure out which magic rows to insert to make RT fully recognize my inserted user, but I never got it to work.

But there is a happy ending anyway: I took another working account, from some guy who quit probably 10 years ago, and re-purposed it into the account I needed. This worked just fine…and is probably what I should have done in the first place!
Kendric Beachey-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Beachey, Kendric
Sent: Friday, September 06, 2013 2:56 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Inserting a user with mysql INSERT

I need to create an account for a catch-all email address that will be sending requests to our RT from a separate workflow. No matter which user triggers the action, the email will appear to come from product.suport@company.com.

When I try to use the GUI to create the user, it fails…looking at the log file, it seems to be because it can’t find an equivalent user in our company-wide Active Directory. (This is a useful thing to seed most user details…name, department, phone, etc. for real people.)

I don’t need all the details for this user, so I decided I’d be OK to have the user created without all the extra goodies, and went right to the mysql command line.

insert into Users set Name=‘productsupport’, EmailAddress=‘product.support@company.com’;

This succeeded fine…I can see the row is in the database. But when I try to call up the user from the admin GUI, it says it can’t find it. Are there other fields I should fill in? Are there actually other tables that need rows inserted too?
Kendric Beachey

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.

The crickets and I poked around in other tables, trying to figure out which magic rows to insert to make RT fully recognize my inserted user, but I never got it to work.

I suspect you forgot to temporarily disable this
https://metacpan.org/source/TSIBLEY/RT-Authen-ExternalAuth-0.17/etc/RT_SiteConfig.pm#L65

But there is a happy ending anyway: I took another working account,
from some guy who quit probably 10 years ago, and re-purposed it into
the account I needed. This worked just fine…and is probably what I
should have done in the first place!

You’ll have some weird results doing this, since any old tickets
associated with that guy will now be associated with this user.

-kevin