You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by Apache Wiki <wi...@apache.org> on 2009/07/28 15:44:34 UTC
[Couchdb Wiki] Trivial Update of "Authentication and Authorization" by
AdamKocoloski
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.
The following page has been changed by AdamKocoloski:
http://wiki.apache.org/couchdb/Authentication_and_Authorization
------------------------------------------------------------------------------
the Erlang/OTP installation directory.
If not specified in local.ini, the authentication handler specified in default.ini,
- {couch_http, default_authentication_handler}, will be used.
+ {couch_httpd, default_authentication_handler}, will be used.
The specified handler is called in couch_httpd::handle_request:
@@ -125, +125 @@
== Authentication handlers ==
- === couch_http::default_authentication_handler ===
+ === couch_httpd::default_authentication_handler ===
If the http request contains basic authentication, the user name and password are checked
against a configured user list. If the user is recognized as an administrator, the user name and
@@ -136, +136 @@
defined, then the _admin role is added to the context.
- === couch_http::null_authentication_handler ===
+ === couch_httpd::null_authentication_handler ===
Any request is granted the <<"_admin">> role.
- === couch_http::special_test_authentication_handler ===
+ === couch_httpd::special_test_authentication_handler ===
If the WWW-Authentication header has a value like "X-Couch-Test-Auth username:password",
the user name and password are checked against a hard-coded list of username/password
@@ -152, +152 @@
[http://issues.apache.org/jira/browse/COUCHDB-420 COUCHDB-420] implements an
[http://oauth.net/ OAuth] authentication handler. The patch also changes
- couch_http to accept a list of authentication handlers instead of a single
+ couch_httpd to accept a list of authentication handlers instead of a single
authentication handler.
Steps to get OAuth authentication working (with the patch installed):