diff options
Diffstat (limited to 'docs/howto/auth-remote-user.txt')
| -rw-r--r-- | docs/howto/auth-remote-user.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/howto/auth-remote-user.txt b/docs/howto/auth-remote-user.txt index fc16647098..742c0d223b 100644 --- a/docs/howto/auth-remote-user.txt +++ b/docs/howto/auth-remote-user.txt @@ -111,8 +111,8 @@ Using ``REMOTE_USER`` on login pages only The ``RemoteUserMiddleware`` authentication middleware assumes that the HTTP request header ``REMOTE_USER`` is present with all authenticated requests. That -might be expected and practical when Basic HTTP Auth with ``htpasswd`` or other -simple mechanisms are used, but with Negotiate (GSSAPI/Kerberos) or other +might be expected and practical when Basic HTTP Auth with ``htpasswd`` or +similar mechanisms are used, but with Negotiate (GSSAPI/Kerberos) or other resource intensive authentication methods, the authentication in the front-end HTTP server is usually only set up for one or a few login URLs, and after successful authentication, the application is supposed to maintain the |
