Building Upon the Concept from AutogeneratedPassword (fwd)

It occured to me that the passwords are encrypted in the database, which
is likely the reason this isn’t trivial. Is the password encryption
one-way? Is this something I could turn off?

The customers we have using RT love the SelfService interface, but as I
mentioned, they tend to forget their password. Has anyone else done up
something like a “Forgot password, send me a new one”-type functionality
that they would be willing to share? This has become quite an
administration headache for me.

-jd---------- Forwarded message ----------
Date: Mon, 13 Feb 2006 05:46:37 -0500 (EST)
From: doogles@doogles.com
To: rt-users@lists.fsck.com
Subject: [rt-users] Building Upon the Concept from AutogeneratedPassword

RT Users–

(I’m running RT 3.4.5.)

I recently modified my Autocreate templates to include the logic suggested in
the AutogeneratedPassword page in the BestPractical wiki. This works well.
However, my user base has a usage pattern which has them interfacing with RT
"once and awhile", and they tend to forget what their password is.

I would like to build upon the AutogeneratedPassword template to email
username/password every time they open up a ticket.

I tried a couple of different things without success. Would anyone care to
suggest the ‘right’ way to accomplish this? I would be happy to update the
Wiki after I successfully implement this.

Thanks!,
-jd
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Download a free sample chapter of RT Essentials from O’Reilly Media at
http://rtbook.bestpractical.com

WE’RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at
http://bestpractical.com/services/training.html

Hi Steven, All

New to RT software, but was thinking on this scenario:

  • User A logs into RT
  • User A is really busy changing tickets
  • User B requests a password change using User A’s email

Will the system prompt User A in the next submit he makes?

Regards,

-Urivan Flores Saaib-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Steven
Platt
Sent: Thursday, February 16, 2006 8:32 AM
To: ‘doogles@doogles.com’; rt-users@lists.fsck.com
Subject: RE: [rt-users] Building Upon the Concept from
AutogeneratedPassword (fwd)

Hi jd,

We’ve recently implemented a PHP driven password reminder system for our
self-service users. They enter an e-mail address which is checked
against
the DB (we use postgres8). Valid addresses get login details e-mailed
back
out to the supplied address.
http://www.hpa-bioinfosupport.org.uk/RT/

AFAIK it’s not possible to easily backtrack from an MD5 encrypted
string, so
our system involves resetting the password to a standard pattern within
the
system. Resetting the password seems to be the best way, but I’m
prepared
(and expecting) to be corrected.

Steve

Steve Platt
Bioinformatics Support Co-ordinator
Bioinformatics Unit: Statistics, Modelling & Bioinformatics Department
Center for Infections
Health Protection Agency
61 Colindale Avenue
London
UK
NW9 5EQ
http://www.hpa.org.uk/srmd/bioinformatics/index.htm

It occured to me that the passwords are encrypted in the database, which
is likely the reason this isn’t trivial. Is the password encryption
one-way? Is this something I could turn off?

The customers we have using RT love the SelfService interface, but as I
mentioned, they tend to forget their password. Has anyone else done up
something like a “Forgot password, send me a new one”-type functionality
that they would be willing to share? This has become quite an
administration headache for me.

See http://wiki.bestpractical.com/index.cgi?PasswordReminder

Travis
Travis Campbell - Unix Systems Administrator = travis@mpdtxmail.amd.com
5900 E. Ben White Blvd, Austin, TX 78741 = travis.campbell@amd.com
TEL: (512) 602-1888 PAG: (512) 604-0341 = webmaster@mpdtxmail.amd.com
"Does anything work as expected?" Yes. An axe through the CPU.