From d5ffc4eb85d71c901c85119cf873e343349e97e2 Mon Sep 17 00:00:00 2001 From: Stefan Fritsch Date: Tue, 5 Jul 2016 23:20:42 +0200 Subject: Imported Upstream version 2.4.23 --- docs/manual/mod/mod_auth_digest.html.en | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) (limited to 'docs/manual/mod/mod_auth_digest.html.en') diff --git a/docs/manual/mod/mod_auth_digest.html.en b/docs/manual/mod/mod_auth_digest.html.en index 14e6f5c6..56c8a0da 100644 --- a/docs/manual/mod/mod_auth_digest.html.en +++ b/docs/manual/mod/mod_auth_digest.html.en @@ -60,28 +60,19 @@
  • AuthDigestQop
  • AuthDigestShmemSize
    • -

    See also

    +

    Bugfix checklist

    See also

    +
  • Comments
    • top

    Using Digest Authentication

    -

    To use MD5 Digest authentication, simply - change the normal AuthType Basic and - AuthBasicProvider - to AuthType Digest and - AuthDigestProvider, - when setting up authentication, then add a - AuthDigestDomain directive containing at least the root - URI(s) for this protection space.

    - -

    Appropriate user (text) files can be created using the - htdigest tool.

    +

    To use MD5 Digest authentication, configure the location to be + protected as shown in the below example:

    Example:

    <Location "/private/">
     AuthType Digest
@@ -94,6 +85,14 @@
 </Location>
    +

    AuthDigestDomain + should list the locations that will be protected by this + configuration.

    + +

    The pasword file referenced in the AuthUserFile directive may be + created and managed using the htdigest tool.

    + +

    Note

    Digest authentication was intended to be more secure than basic authentication, but no longer fulfills that design goal. A -- cgit v1.2.3