On Mar 16, 2007, at 10:37 AM, Mark Graham wrote:

Hello there,


Earlier this week we migrated to the newest release of RT. We are experiencing a problem, specifically, with password migration from the old database to the new database. It seems that RT used todo something funny with character storage - like a character conversion to the string before storing the md5 hash. The new one no longer does that. I've gone through the FAQ and searched the mailing list archives, but I cannot come up with something that would let me migrate this better. Everything did copy over bit for bit, but the old version uses a slightly different encoding for some characters and the new one is straight md5



Hm. RT _should_ be transparently using passwords from old RT instances...all the way back to RT 1.0. It might be another issue.

-jesse

Any suggestions??



Mark Graham

Network Administrator





_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Attachment: PGP.sig
Description: This is a digitally signed message part

_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Reply via email to