Questions on usernames and passwords

Hi,

Are RT usernames case sensitive?

I am creating a CanonicalizeAddress routine for my employer’s use. It
would do

$email =~ s/@.*ourdomain.com//i;
return $email;

(Since the part before ‘@’ in my company is unique, this is ok I expect.)

People tend to write their email address with different cases - I write
mine as BinandS@ourdomain.com, for example. I am already a user with
id ‘binands’ in RT (with various rights). So will that create a new
user? Should I make it do

$email =~ tr/A-Z/a-z/;

before returning?

Another question: I want to assign a password and mail it back if the
ticket is indeed from someone in ourdomain.com - I am fiddling around
with Email.pm. What I need is to assign a default password (generated
via mkpasswd) and possibly ModifySelf too.

I plan to add:
(All this in the else branch of the if inside GetCurrentUser)

my $pwd = undef;
if ($Address !~ /@/) {
$pwd = /usr/bin/mkpasswd -s 0;
}

And then call $NewUser->Create (Passwd => $pwd);

Now I need to mail this password to the user. :frowning: But by this time,
I have lost the email address. :frowning: I can of course append ourdomain.com
(hardcode this in), but is there a better way?

Also, I need to assign the right - how do I do that? Or do I give EveryOne
ModifySelf right?

RT is on RH 7.3 + updates, Apache 1.3.27, fastcgi, RHDB (ie, Postgres).

Binand

I am creating a CanonicalizeAddress routine for my employer’s use. It
would do

$email =~ s/@.*ourdomain.com//i;
return $email;

(Since the part before ‘@’ in my company is unique, this is ok I
expect.)

No, it isn’t ok since RT will send mail to that address. And you
probably get mail from other domains too, right?

Another question: I want to assign a password and mail it back if the
ticket is indeed from someone in ourdomain.com

Jesse posted a template snippet back in November:
< http://lists.fsck.com/pipermail/rt-users/2002-November/010705.html >

You’d just need to a add a check for your domain.

(BTW, why are the messages in the list archive not properly MIME
decoded?)

Sebastian

Sebastian Flothow
sebastian@flothow.de
#include <stddisclaimer.h>

Hi,

As far as I understood, you have already some kind of
external user database, and want to create those users in RT.

Why don’t you try to utilize some kind of external user authentication
(this way the passwords are the same everywhere), and
user importing?

There are solutions with LDAP, which work fine with
Microsoft Exchange/Active directory, and with any other LDAP service.

The simpliest way for password management is Apache authentication:
it has plenty different methods, there must be the one that suits you.

Regards,
Stanislav.— “Binand Raj S.” binand@gmx.net wrote:

Another question: I want to assign a password and mail it back if the
ticket is indeed from someone in ourdomain.com - I am fiddling around
with Email.pm. What I need is to assign a default password (generated
via mkpasswd) and possibly ModifySelf too.

I plan to add:
(All this in the else branch of the if inside GetCurrentUser)

my $pwd = undef;
if ($Address !~ /@/) {
$pwd = /usr/bin/mkpasswd -s 0;
}

And then call $NewUser->Create (Passwd => $pwd);

I am creating a CanonicalizeAddress routine for my employer’s use. It
would do

$email =~ s/@.*ourdomain.com//i;
return $email;

(Since the part before ‘@’ in my company is unique, this is ok I
expect.)

No, it isn’t ok since RT will send mail to that address. And you
probably get mail from other domains too, right?

Right. What I posted was indeed the wrong way to do it, which I figured almost
immediately after I hit ‘y’ :frowning:

Another question: I want to assign a password and mail it back if the
ticket is indeed from someone in ourdomain.com

Jesse posted a template snippet back in November:
< http://lists.fsck.com/pipermail/rt-users/2002-November/010705.html >

Thanks. I knew about this post, and had tried to search the archives,
but couldn’t find it.

BTW, anyone who has a private copy of that post that you can bounce
to me? The list archive version has mime junk all over it. :(On Sat, Jan 04, 2003 at 08:19:55AM -0800, Stanislav Sinyagin wrote:

Hi,

As far as I understood, you have already some kind of
external user database, and want to create those users in RT.

Why don’t you try to utilize some kind of external user authentication
(this way the passwords are the same everywhere), and
user importing?

There are solutions with LDAP, which work fine with
Microsoft Exchange/Active directory, and with any other LDAP service.

Ah, the premise is correct - in my organisation, the email addresses
are unique, and we are sort of standardizing on the part before the '@'
as usernames everywhere.

Unfortunately, the mail server does not use LDAP for authentication
(in hindsight, I guess I should have used LDAP).

I am not concerned with tickets opened by people who use other email
addresses - just the ones from @ourdomain.com. If it is from ourdomain.com,
I want the autocreated username to be minus the @ourdomain.com, and the full
email address otherwise. In either case, I want an autocreated password to be
mailed.

I hope that is clear :slight_smile: Let me go back to the drawing board.

Binand

Ah, the premise is correct - in my organisation, the email addresses
are unique, and we are sort of standardizing on the part before the '@'
as usernames everywhere.

Unfortunately, the mail server does not use LDAP for authentication
(in hindsight, I guess I should have used LDAP).

I am not concerned with tickets opened by people who use other email
addresses - just the ones from @ourdomain.com. If it is from ourdomain.com,
I want the autocreated username to be minus the @ourdomain.com, and the full
email address otherwise. In either case, I want an autocreated password to be
mailed.

I hope that is clear :slight_smile: Let me go back to the drawing board.

OK, whatever, it’s yiour setup. But personally, I’d prefer writing an import
script that would create once all your users with generated or imported
passwords.

Good luck,
Stan

I am interested in the same thing— Stanislav Sinyagin ssinyagin@yahoo.com wrote:

— “Binand Raj S.” binand@gmx.net wrote:

Ah, the premise is correct - in my organisation, the email
addresses
are unique, and we are sort of standardizing on the part before the
’@'
as usernames everywhere.

Unfortunately, the mail server does not use LDAP for authentication
(in hindsight, I guess I should have used LDAP).

I am not concerned with tickets opened by people who use other
email
addresses - just the ones from @ourdomain.com. If it is from
ourdomain.com,
I want the autocreated username to be minus the @ourdomain.com, and
the full
email address otherwise. In either case, I want an autocreated
password to be
mailed.

I hope that is clear :slight_smile: Let me go back to the drawing board.

OK, whatever, it’s yiour setup. But personally, I’d prefer writing an
import
script that would create once all your users with generated or
imported
passwords.

Good luck,
Stan


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at
http://fsck.com/rtfm

Your mind is like a parachute. It must be open to be used effectively.

I am creating a CanonicalizeAddress routine for my employer’s use. It
would do

$email =~ s/@.*ourdomain.com//i;
return $email;

(Since the part before ‘@’ in my company is unique, this is ok I
expect.)

No, it isn’t ok since RT will send mail to that address. And you
probably get mail from other domains too, right?

Right. What I posted was indeed the wrong way to do it, which I figured almost
immediately after I hit ‘y’ :frowning:

Another question: I want to assign a password and mail it back if the
ticket is indeed from someone in ourdomain.com

Jesse posted a template snippet back in November:
< http://lists.fsck.com/pipermail/rt-users/2002-November/010705.html >

Thanks. I knew about this post, and had tried to search the archives,
but couldn’t find it.

BTW, anyone who has a private copy of that post that you can bounce
to me? The list archive version has mime junk all over it. :(On Sat, Jan 04, 2003 at 08:19:55AM -0800, Stanislav Sinyagin wrote:

Hi,

As far as I understood, you have already some kind of
external user database, and want to create those users in RT.

Why don’t you try to utilize some kind of external user authentication
(this way the passwords are the same everywhere), and
user importing?

There are solutions with LDAP, which work fine with
Microsoft Exchange/Active directory, and with any other LDAP service.

Ah, the premise is correct - in my organisation, the email addresses
are unique, and we are sort of standardizing on the part before the '@'
as usernames everywhere.

Unfortunately, the mail server does not use LDAP for authentication
(in hindsight, I guess I should have used LDAP).

I am not concerned with tickets opened by people who use other email
addresses - just the ones from @ourdomain.com. If it is from ourdomain.com,
I want the autocreated username to be minus the @ourdomain.com, and the full
email address otherwise. In either case, I want an autocreated password to be
mailed.

I hope that is clear :slight_smile: Let me go back to the drawing board.

Binand