I have a medium-sized Drupal 6 site (about 5 million page views per month and more than 30 thousand registered users), and I need to integrate the OSQA application, Django. I already have many users, roles, and permissions in my Drupal database, and I would like to specify a Django application to use the login and login pages that I already have in Drupal to give my users a single entry point.
I want to keep part of Django authentication because I think OSQA will work better. I also have performance considerations, the Drupal site already gets a lot of traffic and has a very busy database, and I think using a separate database for Django will help.
After some research, I think I could have Drupal register and run the Django login pages in the background to register or log in to the Django app. I plan to do this by writing a couple of views in Django, one for registration and one for login, and Drupal will post a username and password for those views. Of course, I need to disable CSRF in Django for these views, and possibly also publish a secret key that only my Drupal and Django applications know to avoid external sites trying to use these "insecure" Django views.
I know that my Django application may need some user data from Drupal in some cases, and I plan to use the Drupal services module for this.
Would this be a good approach? Any suggestions?
Thank you so much!
performance authentication django drupal
Alexis bellido
source share