StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHelp with Django RemoteUserMiddleware RemoteUserBackend with fresh database
primarykey
Id
5877686
data
AcceptedAnswerId
10420862
AnswerCount
2
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-05-04T02:01:15.360
FavoriteCount
1
LastActivityDate
2013-04-13T22:03:15.797
LastEditDate
2011-05-04T14:27:57.673
LastEditorUserId
541202
OwnerUserId
541202
ParentId
0
PostTypeId
1
Score
3
ViewCount
2561
LastEditorDisplayName
text
Body
The 1.3 release of Django includes the <code>RemoteUserMiddleware</code> and <code>RemoteUserBackend</code> classes to allow Apache to do authentication. See <a href="http://docs.djangoproject.com/en/dev/howto/auth-remote-user/" rel="nofollow">http://docs.djangoproject.com/en/dev/howto/auth-remote-user/</a> I have an initial_data.json that creates a superuser when syncdb is performed. A dumpdata confirms it. But I find that it doesn't seem to login properly with the newly created database. I get an ImproperlyConfigured exception that says: The Django remote user auth middleware requires the authentication middleware to be installed. <pre><code>Edit your MIDDLEWARE_CLASSES setting to insert django.contrib.auth.middleware.AuthenticationMiddleware' before the RemoteUserMiddleware class. </code></pre> The traceback points to <code>RemoteMilddleware.process_request()</code>: <pre><code>def process_request(self, request): # AuthenticationMiddleware is required so that request.user exists. if not hasattr(request, 'user'): raise ImproperlyConfigured(... </code></pre> The DEBUG output from Apache shows that settings in fact have <code>AuthenticationMiddleware</code> and <code>RemoteUserMiddleware</code> in the requested order: <pre><code>MIDDLEWARE_CLASSES ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.auth.middleware.RemoteUserMiddleware', 'django.contrib.messages.middleware.MessageMiddleware') </code></pre> But the request.user attribute is not set, generating the exception. If I look closer at the source code for django.contrib.auth.backends and middleware, I find that <code>AuthenticationMiddleware</code> is registering <code>LazyUser</code> for the request class. But <code>RemoteUserBackend</code> doesn't seem to have the authenticate() method called which is where remote_user gets looked up in the Users table. Is there something I should be doing to get <code>authenticate()</code> to be called in order to create request.user? I can provide more info as needed. This is using SSL, by the way. Does that have some interaction that I didn't anticipate? I should mention that I'm using Apache2.2.14 and <code>mod_wsgi</code>.
Tags
<python><django><django-authentication>
Title
Help with Django RemoteUserMiddleware RemoteUserBackend with fresh database
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USTraveler
UserOwnerUserId
1. USTraveler
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHelp with Django RemoteUserMiddleware RemoteUserBackend with fresh database
 UserUserId
 USTraveler
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POHelp with Django RemoteUserMiddleware RemoteUserBackend with fresh database
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POHelp with Django RemoteUserMiddleware RemoteUserBackend with fresh database
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.