{"action":"created","issue":{"url":"https://api.github.com/repos/christian-marie/kibana3_auth/issues/35","repository_url":"https://api.github.com/repos/christian-marie/kibana3_auth","labels_url":"https://api.github.com/repos/christian-marie/kibana3_auth/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/christian-marie/kibana3_auth/issues/35/comments","events_url":"https://api.github.com/repos/christian-marie/kibana3_auth/issues/35/events","html_url":"https://github.com/christian-marie/kibana3_auth/issues/35","id":343947967,"node_id":"MDU6SXNzdWUzNDM5NDc5Njc=","number":35,"title":"ES5.X API changes break ESProxy","user":{"login":"german23","id":5765251,"node_id":"MDQ6VXNlcjU3NjUyNTE=","avatar_url":"https://avatars0.githubusercontent.com/u/5765251?v=4","gravatar_id":"","url":"https://api.github.com/users/german23","html_url":"https://github.com/german23","followers_url":"https://api.github.com/users/german23/followers","following_url":"https://api.github.com/users/german23/following{/other_user}","gists_url":"https://api.github.com/users/german23/gists{/gist_id}","starred_url":"https://api.github.com/users/german23/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/german23/subscriptions","organizations_url":"https://api.github.com/users/german23/orgs","repos_url":"https://api.github.com/users/german23/repos","events_url":"https://api.github.com/users/german23/events{/privacy}","received_events_url":"https://api.github.com/users/german23/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-07-24T09:05:14Z","updated_at":"2018-08-01T05:52:38Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Hey,\r\n\r\nfirst off i know you no longer support this project. But maybe others encountered this problem too.\r\n\r\nWe run the auth_module with ES 2.4 so far and it works fine. As we try to upgrade to ES5.X we run into this problem:\r\n\r\n```\r\n[23/Jul/2018 13:50:05] \"GET /_nodes HTTP/1.1\" 200 [\"2733\"] 0.0082\r\n[2018-07-23 13:50:05] ERROR Rack::Lint::LintError: Content-Length header was 2733, but should be 18947\r\n        /var/lib/gems/2.3.0/gems/rack-1.5.2/lib/rack/lint.rb:20:in `assert'\r\n        /var/lib/gems/2.3.0/gems/rack-1.5.2/lib/rack/lint.rb:631:in `verify_content_length'\r\n        /var/lib/gems/2.3.0/gems/rack-1.5.2/lib/rack/lint.rb:655:in `each'\r\n        /var/lib/gems/2.3.0/gems/rack-1.5.2/lib/rack/body_proxy.rb:31:in `each'\r\n        /var/lib/gems/2.3.0/gems/rack-1.5.2/lib/rack/handler/webrick.rb:72:in `service'\r\n        /usr/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'\r\n        /usr/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'\r\n        /usr/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'\r\n```\r\n\r\nThe problems seems to be the change of the _nodes API in ES5.X.\r\n\r\nOld _nodes response:\r\n\r\n```\r\n{\r\n  \"cluster_name\": \"clustername\",\r\n  \"nodes\": {\r\n    \"y1F7B0edRxiW5Bzoiwr0kw\": {\r\n      \"name\": \"node1\",\r\n      \"transport_address\": \"192.168.55.5:9307\",\r\n      \"host\": \"192.168.55.5\",\r\n      \"ip\": \"192.168.55.5\",\r\n      \"version\": \"2.4.0\",\r\n      \"build\": \"ce9f0c7\",\r\n      \"http_address\": \"192.168.55.5:9207\",\r\n      \"attributes\": {\r\n        \"tag\": \"node1\",\r\n        \"master\": \"false\"\r\n      },\r\n\r\n```\r\nNew ES5.X response:\r\n```\r\n{\r\n  \"_nodes\": {\r\n    \"total\": 3,\r\n    \"successful\": 3,\r\n    \"failed\": 0\r\n  },\r\n  \"cluster_name\": \"clustername\",\r\n  \"nodes\": {\r\n    \"QCDpwJg1RDW8Dkf7Bu95VA\": {\r\n      \"name\": \"node1\",\r\n      \"transport_address\": \"192.168.55.5:9300\",\r\n      \"host\": \"192.168.55.5\",\r\n      \"ip\": \"192.168.55.5\",\r\n      \"version\": \"5.6.10\",\r\n      \"build_hash\": \"b727a60\",\r\n      \"total_indexing_buffer\": 308700774,\r\n      \"roles\": [\r\n        \"master\",\r\n        \"ingest\"\r\n      ],\r\n```\r\n\r\nI think the auth_module just uses the 1st new part (with the amount of nodes) and thus the content-length check fails.\r\n\r\nI dont expect a solution, but maybe some hints at which files i should look. I try to find a solution myself than and make a fork.\r\n\r\nThank you very much."},"comment":{"url":"https://api.github.com/repos/christian-marie/kibana3_auth/issues/comments/409457467","html_url":"https://github.com/christian-marie/kibana3_auth/issues/35#issuecomment-409457467","issue_url":"https://api.github.com/repos/christian-marie/kibana3_auth/issues/35","id":409457467,"node_id":"MDEyOklzc3VlQ29tbWVudDQwOTQ1NzQ2Nw==","user":{"login":"german23","id":5765251,"node_id":"MDQ6VXNlcjU3NjUyNTE=","avatar_url":"https://avatars0.githubusercontent.com/u/5765251?v=4","gravatar_id":"","url":"https://api.github.com/users/german23","html_url":"https://github.com/german23","followers_url":"https://api.github.com/users/german23/followers","following_url":"https://api.github.com/users/german23/following{/other_user}","gists_url":"https://api.github.com/users/german23/gists{/gist_id}","starred_url":"https://api.github.com/users/german23/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/german23/subscriptions","organizations_url":"https://api.github.com/users/german23/orgs","repos_url":"https://api.github.com/users/german23/repos","events_url":"https://api.github.com/users/german23/events{/privacy}","received_events_url":"https://api.github.com/users/german23/received_events","type":"User","site_admin":false},"created_at":"2018-08-01T05:52:38Z","updated_at":"2018-08-01T05:52:38Z","author_association":"CONTRIBUTOR","body":"Thank you for your response.\r\n\r\nYou are right, authentication/authorization is support out-of-the-box with Kibana5/6. However this all is behind a pay-wall with the X-Pack Subscription so it is not practical. Also Kibana 3 is just much better than all of the newer Kibana releases ;) \r\n\r\nI´ll have a look at the network layer and see what i can find out."}}
{"actor":{"display_login":"german23"}}