I read this gist before creating the ticket. The documentation states
that it *can contain user_ctx. No indication that this is required if I
have use_users_db = false. I'm not sure that this isn't a bug as, it
requires a component to use the baked in _users auth stuff, even though
I've intentionally configured my database to not use this. This is a
change in behavior from what I've expected with couchdb in the past. So
now, even if I have use_users_db = false, I still have to be aware of
how _users works to understand implications of permissions failures.
Wendall
On 04/02/2012 05:39 PM, Filipe Manana (Commented) (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244879#comment-13244879
]
Filipe Manana commented on COUCHDB-1453:
----------------------------------------
Wendall, it's documented in a gist mentioned at:
http://wiki.apache.org/couchdb/Replication#Replicator_database
Gist: https://gist.github.com/832610 (section 8)
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
