8000 runserver_plus with REMOTE_USER ? · Issue #1708 · django-extensions/django-extensions · GitHub
[go: up one dir, main page]

Skip to content

runserver_plus with REMOTE_USER ? #1708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hannylicious opened this issue Feb 14, 2022 · 0 comments · Fixed by #1769
Closed

runserver_plus with REMOTE_USER ? #1708

hannylicious opened this issue Feb 14, 2022 · 0 comments · Fixed by #1769

Comments

@hannylicious
Copy link
hannylicious commented Feb 14, 2022

Just curious if runserver_plus supports the REMOTE_USER option, if so, I can't seem to find a way to make it work (and thusly could use a little guidance).

When running the default python manage.py runserver command I can get it to work with automatically logging in a REMOTE_USER by doing this: REMOTE_USER="johndoe" python manage.py runserver 8000

Then I can use the site locally as 'johndoe' already logged in.

However, when I replace runserver with runserver_plus in that example, it just returns me to the login page - I can't seem to find any configuration that will work with the REMOTE_USER setting and runserver_plus; am I missing something or does that feature not work with runserver_plus command?

confuzeus added a commit to confuzeus/django-extensions that referenced this issue Oct 29, 2022
Django RemoteUserMiddleware and RemoteUserBackend are able
to authenticate users by looking at the REMOTE_USER request header.

In Werkzeug, this header isn't set unlike in Django's
default WSGI server.

This patch add the variable to the Werkzeug environ
if it's set.

Fixes django-extensions#1708
trbs pushed a commit that referenced this issue Dec 25, 2022
Django RemoteUserMiddleware and RemoteUserBackend are able
to authenticate users by looking at the REMOTE_USER request header.

In Werkzeug, this header isn't set unlike in Django's
default WSGI server.

This patch add the variable to the Werkzeug environ
if it's set.

Fixes #1708
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant
0