Robin Becker wrote on 06/28/07 16:13: > I see from this documentation > > http://www.djangoproject.com/documentation/apache_auth/#configuring-apache > > that it is conceptually possible to configure apache authorization using > django. > > However, we have recently decided to de-couple django from mod_python by > using > fastcgi. This is because we wish to allow our django apps to use which ever > python might be appropriate and not restrict to the one for which we have > compiled apache+mod_python. > > Is there any way to have mod_python stuck on Python-2.4 with the controlling > django app use Python-2.5 and do configuration for apache. The only way I can > think of is to create a stub project which runs the auth only. > > I know that theoretically we can advance the apache, but that implies > re-installing wikis etc etc etc and when Python-2.6 comes out and the boss > wants > to use new feature X we'll go through the whole process again. > > Alternatively is there a way to do the reverse ie get django to use a > database > controlled by apache?
You could directly access the database using something like mod_auth_mysql or the like. But the way django stores passwords may be a problem. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
