Migrating to RT4 with external auth

RT Users
1

I have 3.8.10 set up with local users. We will be migrating to 4.0 with
external auth. I’d like to keep the users’ tickets straight but I messed
up when I set up the original database.

The 3.8.10 instance uses local users with first names all in lower case.
Our AD uses first name and last initial, capitalized.

Thus:

3.8.10 -> yan (rt user)
4.0.2 -> YanS (external auth via AD)

Is it possible to migrate my tickets from yan to YanS?

–Yan

2

I have 3.8.10 set up with local users. We will be migrating to 4.0 with
external auth. I’d like to keep the users’ tickets straight but I messed
up when I set up the original database.

The 3.8.10 instance uses local users with first names all in lower case.
Our AD uses first name and last initial, capitalized.

Thus:

3.8.10 → yan (rt user)
4.0.2 → YanS (external auth via AD)

Is it possible to migrate my tickets from yan to YanS?

You might be able to convince LDAPImport to look users up by the email
address in AD and correct the username. Otherwise you’re probably
looking at a one off script. The one off is probably simpler.

-kevin

3

You might be able to convince LDAPImport to look users up by the email
address in AD and correct the username. Otherwise you’re probably
looking at a one off script. The one off is probably simpler.

Is it as simple as changing the username in 3.8.10 before import? I don’t
have that many users ATM and I could change that easily enough.

–Yan

4

You might be able to convince LDAPImport to look users up by the email
address in AD and correct the username. Otherwise you’re probably
looking at a one off script. The one off is probably simpler.

Is it as simple as changing the username in 3.8.10 before import? I don’t
have that many users ATM and I could change that easily enough.

If you have a small number of users, then yes, click in the UI.
Since you were looking for solutions, I assumed you had enough users
to make that painful.

-kevin