Why should I use DACS instead of Apaches mod_access and mod_auth modules (and mod_auth_dbm, mod_auth_ldap, etc.)?
DACS unifies and extends the functionality of these Apache 2.0 modules (and similar ones in Apache 2.2) and is more flexible, customizable, and versatile. DACS includes the ability to access the same password files used by mod_auth, mod_auth_dbm, and mod_auth_digest. Although we have the utmost respect for the Apache web server, we believe that in many cases DACS offers simpler, cleaner, and more easily understood solutions than does Apache with its assortment of modules. You can continue to use Apache’s authentication modules if you like – DACS can import identities that they establish – together with the authentication mechanisms provided directly by DACS. DACS can happily coexist with Apache’s other access control and authentication modules, so legacy configuration can remain unchanged. DACS can use RFC 2617 HTTP authentication (Basic and Digest), which is supported by most web browsers and HTTP client libraries. A username and password obtained by DACS through this mechanism can be