Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <k7h4av$44p$1@ger.gmane.org>
References: <20121011164501.5b4b2c54@eee-az>
	<k7h4av$44p$1@ger.gmane.org>
Date: Thu, 8 Nov 2012 21:28:37 +0000
Message-ID: 
 <CABvT1DHPMHwSyB0COZ96VXuOHQdsC35kk5_EEX_BtKS8otPz3Q@mail.gmail.com>
Subject: Re: can replicator work with cookies somehow?
From: Robert Newson <rnewson@apache.org>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=047d7bacc07eaacda004ce0284d1

--047d7bacc07eaacda004ce0284d1
Content-Type: text/plain; charset=ISO-8859-1

You can use cookie auth for the replication using this little known API
variant;

"target":{"url" : "http://host:port/db",
"headers":{"cookie":"AuthSession=foo"}}

B.


On 8 November 2012 20:22, bsquared <bwcode4u@gmail.com> wrote:

> On 10/11/2012 06:45 AM, svilen wrote:
>
>> i need to start replications on behalf of a user.
>>
>> i see there's basic http user/psw authtenticaion, and some form of
>> oauth.
>> basic http means i have to keep usr/psw around, and use them when i need
>> replication.
>> but i'd like to avoid storing that usr/psw.
>>
>> as i see there are cookies (via /_session), can replicator work with
>> cookies somehow?
>>
>> or if not, how can i use oauth given there's no 3rd party involved
>> (facebook/twitter/..)? e.g. some kind of degenerate made-up-myself?
>>
>> ciao
>> svil
>>
>>   I believe the credentials have to be supplied in the URL ie.
> https://user:password@couchdb_**instance[:port].
>
> There is a gist on github that covers the replicator db.
>
> gist.github.com/832610
>
>
> --
> Regards,
> Brian
>
>

--047d7bacc07eaacda004ce0284d1--