[COUCHDB-636] proxy authentification handler

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11, 1.0
• Fix Version/s: 0.11
• Assignee: Unassigned
• Reporter: Benoit Chesneau
• Created: 02/Feb/10 14:54
• Updated: 28/Dec/10 23:28
• Resolved: 02/Feb/10 21:07

Description

Find attached a patch that add a proxy authentification handler to couch_httpd_auth.

This handler allows creation of a userCtx objec from a user authenticated remotly. The client just pass specific headers to CouchDB and the handler create the userCtx. Headers name can be defined in local.ini. By thefault they are :

• X-Auth-CouchDB-UserName : username, (x_auth_username in couch_httpd_auth section)
• X-Auth-CouchDB-Roles : user roles, list of roles separated by a comma (x_auth_roles in couch_httpd_auth section)
• X-Auth-CouchDB-Token : token to authenticate the authorization (x_auth_token in couch_httpd_auth section). This token is an hmac-sha1 created from secret key and username. The secret key should be the same in the client and couchdb node. secret key is the secret key in couch_httpd_auth section of ini. This token is optional if secret key isn't defined.