[jira] Closed: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kempf closed COUCHDB-720. Fix Version/s: 0.11.2 Resolution: Fixed With the replication bugfixes for secured databases introduced in CouchDB 0.11.2 replication is now working fine - excellent!! Pull replication fails due to 401 Authentication required while push replication works fine - Key: COUCHDB-720 URL: https://issues.apache.org/jira/browse/COUCHDB-720 Project: CouchDB Issue Type: Bug Components: Futon, HTTP Interface, Replication Affects Versions: 0.10.1, 0.11 Environment: Remote server having Nginx reverse proxy and basic authentication enabled Reporter: Jochen Kempf Priority: Blocker Fix For: 0.11.2 Pull replication fails using both Futon Replicator and http request throwing an 401 Authentication required error. This just happens when design documents are existent. Push replication on the other hand works fine. See used code here: http://gist.github.com/364072 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896905#action_12896905 ] Jochen Kempf commented on COUCHDB-720: -- Still struggeling I did another trial using fresh CouchDB installs on both server and client running Ubuntu 10.04. CouchDB versions are 0.11.1. I am using the nginx and iptables configuration listed here: https://gist.github.com/3b71763abdcd0f1ebd33 The couchdb log is also listed on the previous mentioned gist. As a few of you did manage to get replication working using ssl and nginx I must do something wrong. I would be so happy to get your help to finally figure out the problem and use CouchDB in a secure manner. Due to these problems I have to pass CouchDB credentials without ssl protection :-( Thanks for your help! Pull replication fails due to 401 Authentication required while push replication works fine - Key: COUCHDB-720 URL: https://issues.apache.org/jira/browse/COUCHDB-720 Project: CouchDB Issue Type: Bug Components: Futon, HTTP Interface, Replication Affects Versions: 0.10.1, 0.11 Environment: Remote server having Nginx reverse proxy and basic authentication enabled Reporter: Jochen Kempf Priority: Blocker Pull replication fails using both Futon Replicator and http request throwing an 401 Authentication required error. This just happens when design documents are existent. Push replication on the other hand works fine. See used code here: http://gist.github.com/364072 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885235#action_12885235
]
Jochen Kempf commented on COUCHDB-720:
--
Here are the details of my system configuration in order to help you reproduce
the issue:
- Remote Machine: Ubuntu 10.04 Server, Nginx Webserver with SSL (self signed
certificate and applying this configuration:
http://www.friendpaste.com/2VzN9vD63KV6JDUWQdIT1X), CouchDB 0.11, CouchDB
Lucene -0.6.0, CouchDB Authentication is disabled by setting the null
authentication handler
- Local Machine: Ubuntu 9.10, CouchDB 0.11
Databases to be replicated must have at least one design document to trigger
the issue. I would recommend to trigger a pull replication on the local machine
with the remote DB having the design document and the local machine not. Then
the replication process should freeze once the desing document on the remote
machine is hit.
I used the full url syntax for replication (both in Futon and console):
{target: http://user:passw...@localhost:5984/db;, source:
http://user:passw...@remote/db} - thus the remote machine directly redirects
to the 5984 port without need to specify it.
I hope you can reproduce and fix that issue before the 1.0 release as I really
cannot use CouchDB in my application due to that issue.
Thanks for your help!
Pull replication fails due to 401 Authentication required while push
replication works fine
-
Key: COUCHDB-720
URL: https://issues.apache.org/jira/browse/COUCHDB-720
Project: CouchDB
Issue Type: Bug
Components: Futon, HTTP Interface, Replication
Affects Versions: 0.10.1, 0.11
Environment: Remote server having Nginx reverse proxy and basic
authentication enabled
Reporter: Jochen Kempf
Priority: Blocker
Pull replication fails using both Futon Replicator and http request throwing
an 401 Authentication required error. This just happens when design
documents are existent.
Push replication on the other hand works fine.
See used code here: http://gist.github.com/364072
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885362#action_12885362 ] Jochen Kempf commented on COUCHDB-720: -- I'll take a look to the nginx proxycache discussion and see if that helps. @Klaus: I already commented the admin line out and additionally deactivated authentication setting the null authentication handler I took a look into the nginx log and here is the same 301 response that freezes replication: 201.215.36.77 - jochen [05/Jul/2010:18:44:18 -0400] GET /mytest/_local%2F4eddf88684f747f720130295073f965a HTTP/1.1 200 426 - CouchDB/0.11.0 201.215.36.77 - jochen [05/Jul/2010:18:44:19 -0400] GET /mytest/_changes?style=all_docsheartbeat=1since=4feed=normal HTTP/1.1 200 145 - CouchDB/0.11.0 201.215.36.77 - jochen [05/Jul/2010:18:44:20 -0400] GET /mytest/_design%2Ftest?open_revs=[\x221-967a00dff5e02add41819138abb3284d\x22]revs=truelatest=true HTTP/1.1 301 0 - CouchDB/0.11.0 Here is a link showing my nginx configuration: http://gist.github.com/464797 I still cannot successfully do pull replications! Pull replication fails due to 401 Authentication required while push replication works fine - Key: COUCHDB-720 URL: https://issues.apache.org/jira/browse/COUCHDB-720 Project: CouchDB Issue Type: Bug Components: Futon, HTTP Interface, Replication Affects Versions: 0.10.1, 0.11 Environment: Remote server having Nginx reverse proxy and basic authentication enabled Reporter: Jochen Kempf Priority: Blocker Pull replication fails using both Futon Replicator and http request throwing an 401 Authentication required error. This just happens when design documents are existent. Push replication on the other hand works fine. See used code here: http://gist.github.com/364072 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12884795#action_12884795
]
Jochen Kempf commented on COUCHDB-720:
--
Daniel,
I tried your configuration with a complete new server setup and indeed I do not
get couchdb errors anymore when triggering a pull replication.
However, I still cannot do pull replication when the source db has design
documents in it.
Once it hits a design document a 301 http response is returned and the
replication process just freezes.
Here is a typical log entry:
[Fri, 02 Jul 2010 20:02:28 GMT] [info] [0.1132.0] 201.215.36.77 - - 'GET'
/rrhh_jobs/_design%2FJob?open_revs=[2854-eee80115b5b381b4f55a44b8cdd6dafb]revs=truelatest=true
301
I deactivated authentication in couchdb setting...
authentication_handlers = {couch_httpd_auth, null_authentication_handler}
What else can I do to make pull replication work?
Pull replication fails due to 401 Authentication required while push
replication works fine
-
Key: COUCHDB-720
URL: https://issues.apache.org/jira/browse/COUCHDB-720
Project: CouchDB
Issue Type: Bug
Components: Futon, HTTP Interface, Replication
Affects Versions: 0.10.1, 0.11
Environment: Remote server having Nginx reverse proxy and basic
authentication enabled
Reporter: Jochen Kempf
Priority: Blocker
Pull replication fails using both Futon Replicator and http request throwing
an 401 Authentication required error. This just happens when design
documents are existent.
Push replication on the other hand works fine.
See used code here: http://gist.github.com/364072
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[
https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12866548#action_12866548
]
Jochen Kempf commented on COUCHDB-720:
--
Daniel,
this is the error I get on the client when using a free test ssl cert (only
appears when doing the pull replication):
[Wed, 12 May 2010 11:51:32 GMT] [error] [0.20.0] {error_report,0.8.0,
{0.20.0,std_error,
File operation error: eacces. Target: ./ssl_alert.beam.
Function: get_file. Process: code_server.}}
[Wed, 12 May 2010 11:51:33 GMT] [error] [0.30930.100] SSL:
certify_certificate: ./ssl_handshake.erl:486:Fatal error: handshake_failure
Pull replication fails due to 401 Authentication required while push
replication works fine
-
Key: COUCHDB-720
URL: https://issues.apache.org/jira/browse/COUCHDB-720
Project: CouchDB
Issue Type: Bug
Components: Futon, HTTP Interface, Replication
Affects Versions: 0.10.1, 0.11
Environment: Remote server having Nginx reverse proxy and basic
authentication enabled
Reporter: Jochen Kempf
Priority: Blocker
Pull replication fails using both Futon Replicator and http request throwing
an 401 Authentication required error. This just happens when design
documents are existent.
Push replication on the other hand works fine.
See used code here: http://gist.github.com/364072
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-720) Pull replication claims authentication required from Nginx - push replication on the other hand works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kempf updated COUCHDB-720: - Environment: Remote server having Nginx reverse proxy and basic authentication enabled (was: Remote server having Nginx reverse proxy) Description: Pull replication fails using both Futon Replicator and http request throwing an 401 Authentication required error. Push replication on the other hand works fine. See used code here: http://gist.github.com/364072 was: Pull Replication doesn't work as Authentication required error is returned from Nginx. However, Push Replication using the same full format url is working fine. Priority: Blocker (was: Major) Component/s: Futon HTTP Interface Replication Pull replication claims authentication required from Nginx - push replication on the other hand works fine Key: COUCHDB-720 URL: https://issues.apache.org/jira/browse/COUCHDB-720 Project: CouchDB Issue Type: Bug Components: Futon, HTTP Interface, Replication Affects Versions: 0.10.1, 0.11 Environment: Remote server having Nginx reverse proxy and basic authentication enabled Reporter: Jochen Kempf Priority: Blocker Pull replication fails using both Futon Replicator and http request throwing an 401 Authentication required error. Push replication on the other hand works fine. See used code here: http://gist.github.com/364072 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (COUCHDB-720) Pull replication fails due to 401 Authentication required while push replication works fine
[ https://issues.apache.org/jira/browse/COUCHDB-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kempf updated COUCHDB-720: - Summary: Pull replication fails due to 401 Authentication required while push replication works fine (was: Pull replication claims authentication required from Nginx - push replication on the other hand works fine) Pull replication fails due to 401 Authentication required while push replication works fine - Key: COUCHDB-720 URL: https://issues.apache.org/jira/browse/COUCHDB-720 Project: CouchDB Issue Type: Bug Components: Futon, HTTP Interface, Replication Affects Versions: 0.10.1, 0.11 Environment: Remote server having Nginx reverse proxy and basic authentication enabled Reporter: Jochen Kempf Priority: Blocker Pull replication fails using both Futon Replicator and http request throwing an 401 Authentication required error. Push replication on the other hand works fine. See used code here: http://gist.github.com/364072 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
