couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dale Harvey <>
Subject Re: Persona and BrowserID integration
Date Mon, 29 Jul 2013 15:24:46 GMT
On the topic of browser_id support in CouchDB, it feels like this is a big
chance to push for usable plugins, should the aim for this not to be
included into core but to be available as a one click install from
futon/fauxton (this and geocouch seem prime candidates)?

This isnt because I dont want browser_id support, I most definitely do, I
recently wrote a node equivalent to Jasons browser_id plugin for the only
reason that it would be easier for users to install / use on their local
CouchDB instance.

But we have a problem of support for anything 3rd party needing to be
merged to core to be usable which is very much conflicting with peoples
ability to get stuff done, the browser_id / geocouch and cors support have
been around a long time but are mostly only available to the dedicated few
(cors did eventually get merged), I would love to see a couchdb where the
browser_id plugin was available to all users of couchdb the day you
finished writing it, not (3?) years later

On 29 July 2013 11:26, Jason Smith <> wrote:

> Perfect, that is exactly what I will need. However, the first
> milestone is rewrite my plugin in a branch, and hit the first
> milestone.
> On Mon, Jul 29, 2013 at 5:19 PM, Dirkjan Ochtman <>
> wrote:
> > On Mon, Jul 29, 2013 at 12:02 PM, Jason Smith <> wrote:
> >> To clarify, "tinfoil hat" mode is actually just a complete
> >> implementation of the RP role, notably that it does not require the
> >> POST to to verify an assertion. Thus, CouchDB
> >> could be used on an intranet where an existing IdP exists. The IdP is
> >> out of scope, but I expect to install one to test CouchDB when that
> >> time comes.
> >
> > This might be useful inspiration:
> .
> >
> > Cheers,
> >
> > Dirkjan
> --
> Nodejitsu

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message