On Feb 13, 1:38 am, pbzRPA wrote:
> Just as a suggestion, if you don't need to customize the get_user()
> method then simply don't have a get_user() method in your custom
> authentication class.
Great, thank you for helping me out. I actually didn't realize there
was a get_user function in Mo
Just as a suggestion, if you don't need to customize the get_user()
method then simply don't have a get_user() method in your custom
authentication class.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to djang
On Feb 13, 2:23 am, paul wrote:
> On Feb 12, 5:03 pm, pbzRPA wrote:
>
> > The middleware looks good. Is your browser maybe not blocking cookies?
> > I have really though hard about it, but without code it's really
> > difficult to get a picture of where the problem may lie. You also said
> > yo
On Feb 12, 5:03 pm, pbzRPA wrote:
> The middleware looks good. Is your browser maybe not blocking cookies?
> I have really though hard about it, but without code it's really
> difficult to get a picture of where the problem may lie. You also said
> you do custom authentication, then why is it th
The middleware looks good. Is your browser maybe not blocking cookies?
I have really though hard about it, but without code it's really
difficult to get a picture of where the problem may lie. You also said
you do custom authentication, then why is it that you printing out the
request in the django
On Feb 12, 4:33 pm, pbzRPA wrote:
> Can you please add a dump of your MIDDLEWARE_CLASSES as it is in your
> settings file.
Sure, here it is:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.
Can you please add a dump of your MIDDLEWARE_CLASSES as it is in your
settings file.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email t
On Feb 12, 3:57 pm, pbzRPA wrote:
> It's going to be difficult to help you out if you using a custom
> authentication.
>
> Take a look at this comment from the django site and tell me if you
> following these rules in your custom authentication.
>
yes, django.contrib.auth.authenticate() is cal
It's going to be difficult to help you out if you using a custom
authentication.
Take a look at this comment from the django site and tell me if you
following these rules in your custom authentication.
"""
Calling authenticate() first
When you're manually logging a user in, you must call authent
Another post because I think I explain my issue a little better
here...
in my case:
1) a successful log in results in a call to a HttpResponseRedirect
that goes straight to the web page I'm specifying.
2) I checked right before this HttpResponseRedirect is called, and the
User object that was r
some more info...
I added "django.core.context_processors.request" to
TEMPLATE_CONTEXT_PROCESSORS
Based on my code below, it seems like the session is storing the
correct user ID for the user that just logged in (I confirmed this by
changing the user ID in the database manually), but for some re
On Feb 12, 1:54 am, bruno desthuilliers
wrote:
> On Feb 12, 9:40 am, paul wrote:
>
> > hi -- after I do a login that successfully goes through a custom
> > authenticate() and django login(), I get redirected to a web page that
> > is build off of a template that prints out the value of
> > {{ u
On Feb 12, 9:40 am, paul wrote:
> hi -- after I do a login that successfully goes through a custom
> authenticate() and django login(), I get redirected to a web page that
> is build off of a template that prints out the value of
> {{ user.is_authenticated }}. This always returns False, and aft
13 matches
Mail list logo
