couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Couchdb Wiki] Trivial Update of "Security_Features_Overview" by SebastianCohnen
Date Thu, 08 Apr 2010 18:18:01 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Security_Features_Overview" page has been changed by SebastianCohnen.
The comment on this change is: fixed header.


  An overview of security features focusing on what CouchDB provides out of the box.
- === Authentication ===
+ == Authentication ==
  CouchDB ships with basic authentication that compares user credentials to Admin accounts.
See [[Setting_up_an_Admin_account]] for more details.
  You can specify a custom authentication handler and the web authentication scheme in the
configuration file. The example below specifies that CouchDB will use the default_authentication_handler
method defined in the [[|couch_httpd]]
@@ -17, +17 @@

  Other notes: The "null_authentication_handler" in "couch_httpd" allows any user credentials
to run as admin. Web servers such as Apache or Nginx can also provide an authentication layer
as a reverse-proxy to CouchDB.
- === Authorization ===
+ == Authorization ==
  CouchDB supports one role, the "admin" group, which can execute any of the HTTP API on any
database in the CouchDB instance. See [[Setting_up_an_Admin_account]] for more details.
  CouchDB does not support other roles at this time. Support for read access restriction is
planned for the 1.0 release. 
- === Validation ===
+ == Validation ==
  See [[Document_Update_Validation]].

View raw message