[Couchdb Wiki] Trivial Update of "Security_Features_Overview" by SebastianCohnen

[Apache Wiki <wi...@apache.org>]

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.
http://wiki.apache.org/couchdb/Security_Features_Overview?action=diff&rev1=9&rev2=10

--------------------------------------------------

  
  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 [[http://svn.apache.org/viewvc/couchdb/trunk/src/couchdb/couch_httpd.erl?view=markup|couch_httpd]] module:
@@ -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]].