3 ms·
I've been keeping an eye on PouchDB for a while; it looks like a lot of fun. How does authentication with the Couch server work, though? I don't see anything on
by napoleond 13y ago
I've been keeping an eye on PouchDB for a while; it looks like a lot of fun. How does authentication with the Couch server work, though? I don't see anything on the FAQ or after a brief perusal. CouchDB's apparently lax attitude toward security years ago was what kept me away, but I've always hoped/assumed that it improved since then. Has it?
- daleharvey 13y agoCouchDB had some quirks related to user accounts as it has the added burden of trying to be an application server as well as a database server. With PouchDB a lot of the application server logic doesnt apply and you can use CouchDB as a private data server that requires any connection to be authenticated, in the example we use basic auth but other methods are available and none of the security quirks with 'couchapps' apply. And yes it is a lot of fun :)
- maratd 13y ago> With PouchDB a lot of the application server logic doesnt apply How do I keep one user from accessing another user's data?
- janl 13y agoBy giving each user their own database :)
- maratd 13y agoWhat will stop one user from accessing another user's database?
- daleharvey 13y agoYou can configure databases to require the correct user to authenticate before touching it..
- etrepum 13y agoSadly it's not possible to have CouchDB make that happen for you! You can very easily allow unauthenticated requests to create users, but there's no way to create those per-user databases without writing some trusted code that runs separately from CouchDB.