commit | 473471907c1835f1877805023cfd13ecd3e2ac3a | [log] [tgz] |
---|---|---|
author | Klaus Trainer <klaus_trainer@posteo.de> | Tue Aug 18 16:45:49 2015 +0200 |
committer | Klaus Trainer <klaus_trainer@posteo.de> | Tue Aug 18 17:01:32 2015 +0200 |
tree | 6cc01111ef474bf48fc43a514d486362e9fcad94 | |
parent | 124480e8400f341230815c475ae2daebeabc8e87 [diff] |
Update security object after a user is deleted If the `delete_dbs` configuration value is `false`, we now remove the user name from each the security object's `members` and `admins` element's `names` list, respectively.
couchdb_peruser is a CouchDB daemon that ensures that a private per-user database exists for each document in _users. These databases are writable only by the corresponding user. Databases are in the form:
userdb-{hex encoded username}
For example, the user bob
will have a database named userdb-626f62
.
The reason for hex encoding is that CouchDB usernames have no restrictions, but CouchDB databases have restrictions. Hex encoding the UTF-8 representation of the username is a transformation that's easy to correctly implement in just about any language, especially JavaScript and Erlang. Other encodings would be possible, but would require additional client and server-side code to support that encoding. This is the simplest scheme that is obviously correct.