> Hello Jonas, > > thanks again for your reply. I think migrating the database over to > django may be a good idea, however it's still being used as a legacy > authentication database for other projects. > > In case I'd decide to migrate the existing users over to the new > database, how could I make sure the passwords end up in django > correctly? All I have is the old_password()-crypted user passwords, > can I simply insert those as values into the auth_user db field?
That might be one of the bigger things to overcome. In order to succeed you must find out how django stores passwords and how your current passwords are stored. That way you can start converting , probably by writing some python conversion script. You can find out more on how django stores it's passwords here http://docs.djangoproject.com/en/dev/topics/auth/#passwords For the Zope part you're on you're own, I've never looked at it in my life. > > All the best, Uwe > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > Jonas Geiregat jo...@geiregat.org -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
