I am autocreating users from apache client certificate authentication.
Everyone in my organization can access the site.
However, there is a problem. Let’s say John has never logged into RT.
Then, he sends a mail to the system. An unprivileged account is created
for him. Afterwards, he logs into the system and a privileged account is
created.
But his email was already in the system, so his email is not associated
with his account. If I try to change by hand, I get ‘email address
already in use’.
Is it possible to avoid this behaviour? Running RT-3.8.
Thanks in advance,
-Eduardo
I am autocreating users from apache client certificate
authentication. Everyone in my organization can access the site.
However, there is a problem. Let’s say John has never logged into
RT. Then, he sends a mail to the system. An unprivileged account is
created for him. Afterwards, he logs into the system and a
privileged account is created.
But his email was already in the system, so his email is not
associated with his account. If I try to change by hand, I get
‘email address already in use’.
Is it possible to avoid this behaviour? Running RT-3.8.
You can fix it by searching for the Unprivileged user and changing the
username to John.
You can change it longer-term by writing a local/lib/RT/User_Local.pm
which overrides CanonicalizeUserInfo and causes the username to be
correct from the start.
-kevin
El 18/11/11 17:33, Kevin Falcone escribi�:> On Fri, Nov 18, 2011 at 10:23:01AM +0000, Eduardo Suarez-Santana wrote:
Is it possible to avoid this behaviour? Running RT-3.8.
You can fix it by searching for the Unprivileged user and changing the
username to John.
You can change it longer-term by writing a local/lib/RT/User_Local.pm
which overrides CanonicalizeUserInfo and causes the username to be
correct from the start.
Do you mean searching in the database? Or is that possible via web
interface? Afaik, it is not possible to search for unprivileged users in
the web interface, is it?
I’d also like the user to be privileged. Is there a flag in the database
for that?
Is it possible to avoid this behaviour? Running RT-3.8.
You can fix it by searching for the Unprivileged user and changing the
username to John.
You can change it longer-term by writing a local/lib/RT/User_Local.pm
which overrides CanonicalizeUserInfo and causes the username to be
correct from the start.
Do you mean searching in the database? Or is that possible via web
interface? Afaik, it is not possible to search for unprivileged
users in the web interface, is it?
Use the autocompleter or the Find all users who match: boxes.
I’d also like the user to be privileged. Is there a flag in the
database for that?
It’s available in the web ui after you search for the user.
-kevin
El 21/11/11 15:38, Kevin Falcone escribi�:> On Mon, Nov 21, 2011 at 09:50:25AM +0000, Eduardo Suarez-Santana wrote:
Do you mean searching in the database? Or is that possible via web
interface? Afaik, it is not possible to search for unprivileged users
in the web interface, is it?
Use the autocompleter or the Find all users who match: boxes.
I’d also like the user to be privileged. Is there a flag in the
database for that?
It’s available in the web ui after you search for the user.
Thanks. I’ll try.