CouchApp user registration

Question

I'm building a standalone couchdb application. These are called couchapps. The idea is that the database itself is served on port 80 and returns HTML and works as the actual website. This is a very powerful idea and I'm entirely amazed by this new concept of having your code live inside your database.

But I'm having some issues with user registration. The one built into couchdb allows for cookies to be set and makes it really easy to plug it into your website. But there's several quite important things missing that my app requires in order to say that it has a "proper" user registration system.

1. There's no signup verification. No email is sent, no captcha is displayed. This means that anyone could spam your _users database and create as many new users as they please.

2. If a user forgets their password there's no facility to help them recover it.

Any idea how I could overcome these issues without doing any hardcore Erlang development at a lower level (not an Erlang guy)? It would also be great if anybody knew if I could be using OAuth to authenticate against Twitter or GitHub accounts and have that integrate seemlessly with how couchdb data is handled (inside validate_doc_update functions).

Thank you

Abysmal

Answer 1

While the built in user database can work, I would not recommend it for the workflow you describe. Here are some other options:

Browser ID

I would really recommend using BrowserID. IrisCouch has provided a plugin to couchdb here:

https://github.com/iriscouch/browserid_couchdb

This will take care of the normal registration workflow.

If you want to take it a step further and have your users "Fairly Anonymous", you can follow the example of this couchapp called "Mingle"

https://github.com/thedod/Mingle

Twitter Integration

Max Ogden's "DataCouch" project has a log in via twitter, although it is using some Node external processors to make it work. See here:

https://github.com/maxogden/datacouch/blob/master/processors/auth/twitterauth.js

Facebook integration

https://github.com/ocastalabs/CouchDB-Facebook-Authentication

OpenID

https://github.com/mcaprari/couchdb-openid

---

I dont think you can use the oauth purely with Couch, as this post suggests:

http://bennolan.com/2011/01/11/couchdb-oath.html

so the closest you will get there is following what Datacouch has done.

Hope these suggestions help.

Soy

Thanks. This is pretty much all the material I've also stumbled upon. And there also seems to be another issue (after talking to Max Odgen) with the Cookie expiration time lasting only until your browser is open... which is totally awful. I'll accept your answer and hopefully 1.2 will fix some of this. – Abysmal

You can use oauth as of 1.3 – Chrestomathy