-
Notifications
You must be signed in to change notification settings - Fork 114
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
Getting the Username #14
Comments
A REMOTE_USER header does get set. |
Alright. I'll take a look at it again on Monday. I had uWSGI dump the headers and REMOTE_USER was not set. On further research, it appears as though it needs to be set in the uwsgi_params setting:
http://trac.nginx.org/nginx/ticket/69 I have not tested this, yet. |
Yes, sorry. We set the nginx variable $remote_user, which you can use to set a header yourself. This is the way, as far as I know, every authentication module in nginx works. |
Yup. You're right. Sorry for the noise. |
How are underlying apps determining the username? I'm attempting to deploy an internal MoinMoin wiki with SPNEGO over Kerberos. I have the Kerberos part down, but MoinMoin doesn't know what the username for the person should be.
Typically, the upstream SPNEGO system will set a header called REMOTE_USER with the username content of the principal name: https://wiki.python.org/moin/HelpOnAuthentication#Given_authentication
The text was updated successfully, but these errors were encountered: