I am trying to avoid creating a user in the first place. From what I have
been able to trace in the RT code, a first class user is created from the
But that’s a bit confusing in our case. We are using our own external
authentication system and when CCs are automatically created, our system
detects the new user and let them request a password. But since we just
want them to be receiving emails, not accessing RT, a password leads them
to confusion. They cannot/should not see anything in RT.
Of course we could change our code to double check if these accounts are
’empty’ (not members of anything). But I was wondering if we could skip
the user account in the first place.
That might be tricky since we still want them to receive correspondence
about the ticket.
ThierryOn Wed, Sep 21, 2016 at 9:05 AM, Matt Zagrabelny email@example.com wrote:
On Tue, Sep 20, 2016 at 4:26 PM, Thierry Thelliez firstname.lastname@example.org wrote:
Under RT 4.2, is it possible to not automatically create a user from the
It is possible to create a user - that has an email address as a
"name". RT uses the field “name” to mean username.
I just tested it on my 4.2 test system and it works.
We would like that the CCed users receive emails from ticket
without creating for class user accounts.
In one email thread from 2015, I saw the reference to a variable:
AutoCreateNonExternalUsers. I am not entirely sure that this is what I
need, but that does not seem to be available in 4.2, correct?
AutoCreateNonExternalUsers makes it sound like it auto creates local
users - I’m not sure how that applies here.
Perhaps that config variable is for an extension or extra module.