Changes between Version 10 and Version 11 of AuthFramework

Timestamp:

Aug 22, 2008, 3:21:26 PM (16 years ago)

Author:

cmlenz

Comment:

--

AuthFramework

@@ -78 +78 @@
 === Development Server Integration ===
 
-As HTTP authentication is generally performed by the web server, testing a web app relying on HTTP authentication is often inconvenient. The Diva DevelopmentServer makes it easy by providing built-in support for HTTP Digest authentication, which can be enabled simply by specifying a couple of command-line options:
+As HTTP authentication is generally performed by the web server, testing a web app relying on HTTP authentication is often inconvenient. The Diva DevelopmentServer makes it easy by providing built-in support for HTTP Basic and Digest authentication, which can be enabled simply by specifying a couple of command-line options:
 
 {{{
@@ -92 +92 @@
 
   Authentication:
+    -B FILE, --basic=FILE
+                        path to an unencrypted password file to use for basic
+                        authentication
     -D FILE, --digest=FILE
                         path to a htdigest file to use for authentication
@@ -102 +105 @@
 }}}
 
-The `--digest` option is used to specify the text file containing the credentials, in a format compatible with the [http://httpd.apache.org/docs/2.2/programs/htdigest.html Apache htdigest tool]. The `--realm` option can be used to specify a different realm, where the default is the name of the `Application` class. This realm needs to match the realm used in the digest file.
+The `--digest` option is used to specify the text file containing the credentials for digest authentication, in a format compatible with the [http://httpd.apache.org/docs/2.2/programs/htdigest.html Apache htdigest tool]. The ``--basic`` option allows you to use an unencrypted password file for even simpler setup. The `--realm` option can be used to specify a different realm, where the default is the name of the `Application` class. This realm needs to match the realm used in the digest file.
 
 Finally, the `--protect` option can be used to require authentication only on the specified sub-resources. When the `--protect` option is not provided, the whole URI space will require authentication. When it is specified, authentication is only required on the specified paths. To protect more than one path, simply specifiy the option as often as you need.