You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@couchdb.apache.org by Pulkit Singhal <pu...@gmail.com> on 2012/06/07 17:02:03 UTC

JSON structure for security object

Has the JSON structure for security object changed in version 1.2.0 to use
the members key instead of readers key?

I ask because the Futon pop-up for the setting the security of a database,
changed its terminology from "readers" to "members" and I find myself
wondering if its a cosmetic change or something more.

I know that at least the current info on the CouchDB wiki doesn't show any
such change but it doesn't hurt to confirm :)
http://wiki.apache.org/couchdb/Security_Features_Overview#Authorization
{
  "admins" : {
     "names" : ["joe", "phil"],
     "roles" : ["boss"]
   },
   "readers" : {
     "names" : ["dave"],
     "roles" : ["producer", "consumer"]
   }
}

Re: JSON structure for security object

Posted by CGS <cg...@gmail.com>.

Hi,

There is an older proposal for separating read from write rights per
database. I don't recall seeing that proposal implemented in 1.2, but it
may be that gave at least an idea to developers that "readers" is not (or
will not be - who knows?) the right word for that part.

CGS

On Fri, Jun 8, 2012 at 6:13 PM, Pulkit Singhal <pu...@gmail.com>wrote:

> Has the JSON structure for security object changed in version 1.2.0 to use
> the members key instead of readers key?
>
> I ask because the Futon pop-up for the setting the security of a database,
> changed its terminology from "readers" to "members" and I find myself
> wondering if its a cosmetic change or something more.
>
> I know that at least the current info on the CouchDB wiki doesn't show any
> such change but it doesn't hurt to confirm :)
> http://wiki.apache.org/couchdb/Security_Features_Overview#Authorization
> {
>  "admins" : {
>     "names" : ["joe", "phil"],
>     "roles" : ["boss"]
>   },
>   "readers" : {
>     "names" : ["dave"],
>     "roles" : ["producer", "consumer"]
>   }
> }
>

JSON structure for security object

Posted by Pulkit Singhal <pu...@gmail.com>.

Has the JSON structure for security object changed in version 1.2.0 to use
the members key instead of readers key?

I ask because the Futon pop-up for the setting the security of a database,
changed its terminology from "readers" to "members" and I find myself
wondering if its a cosmetic change or something more.

I know that at least the current info on the CouchDB wiki doesn't show any
such change but it doesn't hurt to confirm :)
http://wiki.apache.org/couchdb/Security_Features_Overview#Authorization
{
  "admins" : {
     "names" : ["joe", "phil"],
     "roles" : ["boss"]
   },
   "readers" : {
     "names" : ["dave"],
     "roles" : ["producer", "consumer"]
   }
}