[
https://issues.apache.org/jira/browse/COUCHDB-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667764#action_12667764
]
Adam Kocoloski commented on COUCHDB-34:
---------------------------------------
I can submit a patch for this if we decide on the API for specifying
credentials. The JSON object POSTed to _replicate looks like
{
"source": "http://example.com:5984/dbname";,
"target": "dbname",
"source_options": { "headers": [ {K,V} ] },
"target_options: { }
}
Do we want to make clients do the Base64 encoding themselves? In that case,
they can stick the authentication header in the JSON object. Do we want some
alternative option in the _options Objects? Do we want to support
http://user:p...@host:port URLs?
> Enable replicator to use HTTP authentication
> --------------------------------------------
>
> Key: COUCHDB-34
> URL: https://issues.apache.org/jira/browse/COUCHDB-34
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Reporter: Christopher Lenz
> Priority: Blocker
> Fix For: 0.9
>
>
> You can currently give the CouchDB replicator HTTP URIs to remote databases.
> However, if one of those remote instances is behind HTTP authentication, the
> replication will fail. It should be possible to specify authentication
> credentials to the replicator, which it would then use in response to 401
> responses.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
