Hi,
If you really want to be sure that as little secret information as
possible goes through the wire, you can always use oauth, even for
replication:
https://wiki.apache.org/couchdb/Replication#OAuth
--
Matthieu Rakotojaona
signature.asc
Description: PGP signature
On Feb 18, 2014, at 10:18 AM, Jason Winshell wrote:
> (2) the user:password would never be exposed to user other than the server
> administrator on the backup.
If this is a persistent replication, you'd need to secure the '_replicator'
database against unauthorized access, since the URL is a
Works as intended. You can easily verify this with Wireshark.
Jason Winshell wrote:
>Hi folks,
>
>I need to replicate between a master and backup database in a
>high-security environment. Replication, like any interaction with the
>database must be authenticated. Both Couch instances are fronted
Hi folks,
I need to replicate between a master and backup database in a high-security
environment. Replication, like any interaction with the database must be
authenticated. Both Couch instances are fronted by an SSL-proxy. There is no
remote access to the http API (i.e. port 5984) without goin
