Saturday, November 14, 2009

[Rails] Re: authlogic fails on existing accounts when crypted_password is blank

On Fri, Nov 13, 2009 at 4:01 PM, Todd A. Jacobs <tjacobs-sndr-b4faac@codegnome.org> wrote:

I recently ran a migration to add the following to an existing user
model:

   t.string   "crypted_password"
   t.string   "password_salt"
   t.string   "persistence_token"

There is an existing (cleartext) password field, but authlogic doesn't
seem to be reading that on existing accounts. As a result, all logins
for existing accounts fail.

How can I get authlogic to either use the cleartext passwords, or to
bulk-populate the crypted_password and password_salt fields for existing
accounts?


Hi, you might want to take a look at the following screencast:


Good luck,

-Conrad
 
--
"Oh, look: rocks!"
       -- Doctor Who, "Destiny of the Daleks"





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate