Question

Document databases that support REST-style JSON over HTTP access seem ideal for supporting AJAX-rich applications where the browser is making direct calls to the database, bypassing the traditional web server / application logic components. An example of this might be retrieving user preferences once a user has been authenticated. (BBC Homepage might be a good example of this, prior to crashing under the load!)

The problem with this scenario is the security issue – if a user is authenticated using a web server (e.g. basic forms authentication), how is this identity carried over to the document DB. Is the only answer to proxy all requests to the DB through the web server anyway – i.e. secure the document DB so that there is no direct external access?

This seems to make most sense, and is the easiest to implement, but I was wondering whether anyone out there had an experience and / or advice on using document dbs in a heterogeneous environment?

Answer 1

This probably differs in every database you mention. Here’s how it works in CouchDB.

CouchDB allows you to manage users and roles.

You can use the validate_doc_update function in your design documents to restrict document creation/update. For example, you can write a validation that denies document update to anyone but its author.

To restrict who can read documents from a database, you can edit the /db_name/_security document and list the users or roles.

However, I don’t think you can make the read access more granular (i.e. allow a user to read only the documents they created).

To achieve that, you have to put the CouchDB behind a proxy and use views to serve the documents to authenticated users. You can still use CouchDB user management this way. The proxy just hides the direct access to the database.

For more detailed info, check the security overview on CouchDB wiki, the security chapter of the Relax book and this short screencast.