Re: Improperly Configured Remote User Middleware

2011-07-27 Thread Karen Tracey
On Wed, Jul 27, 2011 at 9:50 PM, John  wrote:

> I did check here before posting, clearly not well enough, but I was
> mostly googling for django improperly configured remote user and
> similar stuff. Thanks for the link to the bug. It looks like it was
> fixed, but not committed.
>
>
It was not directly fixed, but the code which was causing the problem has
been restructured, therefore it is believed to be fixed by that other
change, which has been committed.

You'll usually get best results when searching by copy/pasting the error, or
taking verbatim key bits of it like RemoteUserMiddleware.

Karen
-- 
http://tracey.org/kmt/

-- 
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.



Re: Improperly Configured Remote User Middleware

2011-07-27 Thread John
I did check here before posting, clearly not well enough, but I was
mostly googling for django improperly configured remote user and
similar stuff. Thanks for the link to the bug. It looks like it was
fixed, but not committed.

On Jul 27, 7:56 pm, Karen Tracey  wrote:
> Did you try searching this list for RemoteUserMiddleware before banging your
> head too hard against the wall on this one? I know this problem of
> RemoteUserMiddleware masking other errors has come up at least twice on this
> list in the past. It has also hopefully been fixed, 
> seehttps://code.djangoproject.com/ticket/15671
>
> Karen
> --http://tracey.org/kmt/

-- 
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.



Re: Improperly Configured Remote User Middleware

2011-07-27 Thread Karen Tracey
Did you try searching this list for RemoteUserMiddleware before banging your
head too hard against the wall on this one? I know this problem of
RemoteUserMiddleware masking other errors has come up at least twice on this
list in the past. It has also hopefully been fixed, see
https://code.djangoproject.com/ticket/15671

Karen
-- 
http://tracey.org/kmt/

-- 
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.



Re: Improperly Configured Remote User Middleware

2011-07-27 Thread John
Just some further info for anyone who may come across this in the
future, this happened to me a few more times. After the third time it
happened I was hitting my head against the wall and finally noticed a
simple error in a signal handler I was importing into models.py. After
fixing that bug the configuration error went away and I was able to
continue developing the site. So when I said in the second post that I
changed something minor unrelated to the issue, I probably fixed a bug
that was crashing the authentication middleware.

So I believe the issue is:
The middleware files are processed in order
The authentication middleware needs models and so models.py is
imported
The import of models.py fails
The authentication middleware fails to load models properly and so
it fails
The remote user middleware checks for the authentication
middleware which is not properly loaded
It throws the error with message 'remote user middleware needs
authentication middleware...' masking the actual cause of the issue

I am just guessing, I haven't looked at much of the Django internals,
but I am hoping that my experience will be helpful for someone else.

-- 
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.



Re: Improperly Configured Remote User Middleware

2011-07-20 Thread John
I changed my uat instance to point at PostgreSQL instead of SQLite and
now it works. I touched nothing relating to this issue, but it looks
like it worked itself out. I would imagine there was some caching of
something somewhere that was not getting overwritten.

Thanks anyway.

On Jul 20, 12:35 pm, John  wrote:
> I am trying to get sso working with apache and Django. I have the
> REMOTE_USER being filled correctly with
> mod_auth_kerb, and I followed the simple directions listed 
> athttps://docs.djangoproject.com/en/dev/howto/auth-remote-user/
> in an attempt to enable Django's REMOTE_USER authentication.
>
> I am able to successfully start and run my development server with
> manage.py runserver. The authentication fails
> because there is no REMOTE_USER, but I am able to browse around the
> public stuff like normal.
>
> When I try to access it through apache, I get:
>         The Django remote user auth middleware requires the
> authentication middleware to be installed.
>         Edit your MIDDLEWARE_CLASSES setting to insert
> 'django.contrib.auth.middleware.AuthenticationMiddleware'
>         before the RemoteUserMiddleware class.
>
> I then scroll down through the Request Information and see:
>
> MIDDLEWARE_CLASSES
> ('django.contrib.sessions.middleware.SessionMiddleware',
>
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
>
> 'django.contrib.auth.middleware.RemoteUserMiddleware',
>
> 'django.middleware.common.CommonMiddleware',
>
> 'django.middleware.csrf.CsrfViewMiddleware',
>
> 'django.contrib.messages.middleware.MessageMiddleware')
>
> Which matches my settings.py:
>
> MIDDLEWARE_CLASSES =  (
>     'django.contrib.sessions.middleware.SessionMiddleware',
>     'django.contrib.auth.middleware.AuthenticationMiddleware',
>     'django.contrib.auth.middleware.RemoteUserMiddleware',
>     'django.middleware.common.CommonMiddleware',
>     'django.middleware.csrf.CsrfViewMiddleware',
>     'django.contrib.messages.middleware.MessageMiddleware',
> )
>
> I don't get it, am I missing something obvious here? I have tried
> reordering everything, deleting and re-adding the files,
> and googling for a couple of hours. Hopefully someone here will be
> able to point me in the right direction because I am
> out of ideas.
>
> Thanks in advance for any help.

-- 
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.



Improperly Configured Remote User Middleware

2011-07-20 Thread John
I am trying to get sso working with apache and Django. I have the
REMOTE_USER being filled correctly with
mod_auth_kerb, and I followed the simple directions listed at
https://docs.djangoproject.com/en/dev/howto/auth-remote-user/
in an attempt to enable Django's REMOTE_USER authentication.

I am able to successfully start and run my development server with
manage.py runserver. The authentication fails
because there is no REMOTE_USER, but I am able to browse around the
public stuff like normal.

When I try to access it through apache, I get:
The Django remote user auth middleware requires the
authentication middleware to be installed.
Edit your MIDDLEWARE_CLASSES setting to insert
'django.contrib.auth.middleware.AuthenticationMiddleware'
before the RemoteUserMiddleware class.

I then scroll down through the Request Information and see:

MIDDLEWARE_CLASSES
('django.contrib.sessions.middleware.SessionMiddleware',
 
'django.contrib.auth.middleware.AuthenticationMiddleware',
 
'django.contrib.auth.middleware.RemoteUserMiddleware',
 
'django.middleware.common.CommonMiddleware',
 
'django.middleware.csrf.CsrfViewMiddleware',
 
'django.contrib.messages.middleware.MessageMiddleware')

Which matches my settings.py:

MIDDLEWARE_CLASSES =  (
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.auth.middleware.RemoteUserMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
)

I don't get it, am I missing something obvious here? I have tried
reordering everything, deleting and re-adding the files,
and googling for a couple of hours. Hopefully someone here will be
able to point me in the right direction because I am
out of ideas.

Thanks in advance for any help.

-- 
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.