Thanks Filipe for the feedback.
This may be invalid, but documentation is so far behind now, I'm never
sure what is expected behavior and what is a bug. Every new feature from
the last 1+ years is either poorly documented, or not documented at all.
Luckily, I typically use a base feature set that I've been happy with
since 0.10.x. This was a case of trying a new feature, reading the
documentation, and finding that it was not really documented at all.
Wendall
On 04/02/2012 05:01 PM, Filipe Manana (Commented) (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244860#comment-13244860
]
Filipe Manana commented on COUCHDB-1453:
----------------------------------------
Try adding an explicit user_ctx property to the replication document:
{
"source": ...,
...,
"user_ctx": { "roles": [ "_admin"] }
}
Database creation and design document update/creation/deletion requires admin
privilege. This is documented somewhere in the wiki.
Replicator fails with use_users_db = false
------------------------------------------
Key: COUCHDB-1453
URL: https://issues.apache.org/jira/browse/COUCHDB-1453
Project: CouchDB
Issue Type: Bug
Components: Replication
Affects Versions: 1.2
Environment: Centos 6 32bit, Erlang R14B, Spidermonkey 1.8.5
Reporter: Wendall Cada
If I create a new replication document in _replicate like this:
{
"source": "http://localhost:5990/users",
"target": "users_backup",
"create_target": true,
"continuous": true
}
Creation of DB fails with:
"unauthorized to access or create database users_backup"
If I manually create this database, and set create_target to false, replication
completes, but generates errors while processing the update_sequence like this:
Replicator: couldn't write document `_design/lck`, revision
`2-8edc91dec975f893efdc6f440286c79e`, to target database `users_backup`. Error:
`unauthorized`, reason: `You are not a db or server admin.`.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira