Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1CA67E16 for ; Tue, 27 Dec 2011 05:09:36 +0000 (UTC) Received: (qmail 94594 invoked by uid 500); 27 Dec 2011 05:09:35 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94353 invoked by uid 500); 27 Dec 2011 05:09:34 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 93659 invoked by uid 99); 27 Dec 2011 05:09:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Dec 2011 05:09:32 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of randall.leeds@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Dec 2011 05:09:28 +0000 Received: by iazz13 with SMTP id z13so22258648iaz.11 for ; Mon, 26 Dec 2011 21:09:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=W7sXY7H0ulFJya2FB3KSIseK4u1signpsFG72NyB4Cw=; b=SjLMtkSc9dZtFysTgp5u9aSU/qnop0MEKy4vImvxDynnW2utvnht6S8m6FPMHZvtsJ qldSko+hpW5fMZADllZ8PItUHkL35sogOdLGbg9gzCYTkVSS/1ezxQgM5zhWJvfRwTLA YTGk2JAe5MSlafV4TGFAyA86MHHsDwlyH/ipc= MIME-Version: 1.0 Received: by 10.50.180.130 with SMTP id do2mr29543720igc.23.1324962548201; Mon, 26 Dec 2011 21:09:08 -0800 (PST) Received: by 10.42.213.194 with HTTP; Mon, 26 Dec 2011 21:09:08 -0800 (PST) In-Reply-To: References: <4EF7D9C4.9050404@netsend.nl>

Date: Tue, 27 Dec 2011 00:09:08 -0500 Message-ID: Subject: Re: browserid support From: Randall Leeds To: user@couchdb.apache.org, dev@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 On Sun, Dec 25, 2011 at 22:02, Jason Smith wrote: > On Mon, Dec 26, 2011 at 9:51 AM, Michiel de Jong wrote: >> The other thing, CouchDB as a BrowserId RP, would simply be instead of >> clicking 'login' at the bottom right in futon, there would be a BrowserId >> sign in button there. This is nice because then people don't have to >> remember their CouchDB password all the time. Or for that matter, their >> password in whatever app uses CouchDB. This would have to be something in >> front of CouchDB, which check the BrowserId assertion, and opens a session >> - which may involve storing the plain text admin password and sending this >> to the client, or creating a session token and staying inbetween as a >> proxy, or creating a session token and adding this into the _users database >> as you send it in plain text to the client. > > We are further along than that. CouchDB can confirm a valid BrowserID > identity (however it uses the mozilla.org web service). But the > experience for the Couch application developer is quite good (IMO). > > https://github.com/iriscouch/browserid_couchdb > > -- > Iris Couch As Jason points, out, CouchDB can already act as an RP with the BrowserID plugin mentoined. I still have a lot of interest in making CouchDB both a primary identity provider and a verifier, but I've lost track of the state of BrowserID. I'm including dev@ in the hopes that a discussion about implementation can grow there. -Randall