I’m just about ready to cut over to our new 3.4.1 install from 2.1.15, but I’ve ran into an issue. On
our old instance of RT all users were created with their email address as there username. On our
new instance we have Apache using Active Directory for authentication. The username that they
use for AD is different from their email address. For example joe.smith@example.com is user
s123456. I’d like for the users to be able to see their old tickets created with their joe.smith@example.com login when we cut over to use the s123456 login. Is there a sane way
of doing this without screwing up RT?
Matt
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act (“E-Sign”)
unless a specific statement to the contrary is included in this message.
I’m just about ready to cut over to our new 3.4.1 install from 2.1.15, but I’ve ran into an issue. On
our old instance of RT all users were created with their email address as there username. On our
new instance we have Apache using Active Directory for authentication. The username that they
use for AD is different from their email address. For example joe.smith@example.com is user
s123456. I’d like for the users to be able to see their old tickets created with their joe.smith@example.com login when we cut over to use the s123456 login. Is there a sane way
of doing this without screwing up RT?
Matt
You should be able to just rename the users. RT doesn’t store
a reference to the username or e-mail address anywhere. Just
the used id number.
I’m just about ready to cut over to our new 3.4.1 install from 2.1.15, but I’ve ran into an issue. On
our old instance of RT all users were created with their email address as there username. On our
new instance we have Apache using Active Directory for authentication. The username that they
I would recommend using the ldap overlay. I have not tested
this updated version, but its’ predecessor is straightforward and
works well.
use for AD is different from their email address. For example joe.smith@example.com is user
s123456. I’d like for the users to be able to see their old tickets created with their
You’ll probably want to change the ‘username’ for all users in RT to
their associated AD username. That should address your concern of
around user/ticket associations.
joe.smith@example.com login when we cut over to use the s123456 login. Is there a sane way
of doing this without screwing up RT?
I think the only sane way to do what you want is to compromise with the
‘Ldap Overlay’, and change your RT account usernames.