Why not use the user table in the old DB for everything instead of duplicating the information in both tables?
On Apr 21, 10:01 am, DanC <[email protected]> wrote: > Hi, > > I was wondering if anyone is familiar with restful_authentication > plugin. > > I have an app which uses restful_authentication and I am creating a > new app which will exist at a seperate url. However, I would like > users who have registered on app1 to be able to log into app2 without > having to register again. > > For new members I am going to use establish_connection to save the > user to 2 databases. > > But for existing members I have tried importing the existing columns > from the user database in app1 (encrypted_password, salt etc.) to the > user database in app2 which has the same columns, but the log in does > not work. > > Can anyone suggest why this may be? > > Thanks, > > Dan > > -- > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/rubyonrails-talk?hl=en. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
