maybe the user is already logged in? it is sending the sessionid and the
server is authenticating checking the sessionid
On Thu, Oct 13, 2016 at 10:09 PM, Garry <garry.m.brot...@gmail.com> wrote:
> I'm porting a legacy Django+mod_python application to Django+WSGI on
> Apache httpd 2.4 (Linux) and cannot get user authentication to work. It's
> not that authentication is running and failing or that it's reporting
> errors, it's simply not running at all. When my WSGI-authenticated URL is
> accessed, I do trace into Django code so it's not like I'm completely
> misconfigured but the *check_password* function (and the *login* and
> *authenticate* functions too) are never invoked. Similarly, my configured
> backend database class initializes but its *load* method is never called.
> I'm using out-of-the-box Django authentication classes, have followed
> Django's (excellent) mod_wsgi integration instructions
> and still don't see any attempt at authentication. I'm at a loss how to
> debug this further; thoughts or suggestions, please?
> Thanks, Garry
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to firstname.lastname@example.org.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.