-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
WsgiDAVApp does not allow upstream authentication #11
Comments
Alternatively, the HTTPAuthenticator could do something similar to
and then change behavior based on whether the REMOTE_USER was provided or not. |
Indeed, and maybe one option could be 'enabled = False'? If you like to propose an implemetation or even a Pull request that would be great. Otherwise I will keep it on the Backlog... |
Without changing the interface, a workaround is to copy the upstream username if the HTTPAuthenticator is set to not send any auth response and username is already present. This would require that someone knows the behavior (from config docs) to use it. Here is a minimal diff:
|
I would think this is solved with #3 (configurable WSGI stack) |
I started a branch for this, see #28 |
This is not too big of a deal for me, but I am using WsgiDAVAPP behind Apache HTTP authentication / authorization layer. Currently, there is no way to interrupt the WsgiDAVApp stack to avoid or replace use of HTTPAuthenticator object. This makes it impossible to substitute value for environ['http_authenticator.username'] as HTTPAuthenticator sets it to the empty string if not used.
It would be convenient to have a way to control use of HTTPAuthenticator similar to how the config option "dir_browser" controls use of WsgiDavDirBrowser.
The text was updated successfully, but these errors were encountered: