# Authentication again **URL:** \ **Category:** Elasticsearch\ **Created:** [March 9, 2014, 4:14pm UTC](https://discuss.elastic.co/t/authentication-again/16255 "2014-03-09T16:14:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Martin\_Hatas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martin_hatas/32/1742_2.png) [@Martin\_Hatas](https://discuss.elastic.co/u/Martin_Hatas)\ **Post date:** [March 9, 2014, 4:14pm UTC](https://discuss.elastic.co/t/authentication-again/16255/1 "2014-03-09T16:14:15Z")
I know that authentication between nodes (native protocol) is not provided natively by ES. But I have 2 aditional questions: 1. Do you consider to put this functionality to the roadmap (in the near future)? 2. Have anyone solved this issue by some homebrewed solution (e.g. by wrapping or extending Node/Client class)? We really recognize ES as brilliant piece of software for MANY reasons but we cann´t intergrate it to our product/solutions mainly due to missing authentication/encryption. Thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/de893a57-fc5f-4ca9-aa80-1440af8dad17%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/de893a57-fc5f-4ca9-aa80-1440af8dad17%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Martin\_Hatas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martin_hatas/32/1742_2.png) [@Martin\_Hatas](https://discuss.elastic.co/u/Martin_Hatas)\ **Post date:** [March 9, 2014, 4:22pm UTC](https://discuss.elastic.co/t/authentication-again/16255/2 "2014-03-09T16:22:21Z")
Cluster access control based on IP/port is not acceptable for us. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9fb41dd5-4ff5-4289-a496-2dfaf5e11baf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9fb41dd5-4ff5-4289-a496-2dfaf5e11baf%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Binh\_Ly\_2](https://avatars.discourse-cdn.com/v4/letter/b/d07c76/32.png) [@Binh\_Ly\_2](https://discuss.elastic.co/u/Binh_Ly_2)\ **Post date:** [March 10, 2014, 5:05pm UTC](https://discuss.elastic.co/t/authentication-again/16255/3 "2014-03-10T17:05:35Z")
Perhaps you can give this a try: > **[sonian/elasticsearch-jetty](https://github.com/sonian/elasticsearch-jetty)** > > Contribute to elasticsearch-jetty development by creating an account on GitHub. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/b457c90d-1b4d-4a79-a051-5751e2609dfe%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b457c90d-1b4d-4a79-a051-5751e2609dfe%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Martin\_Hatas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martin_hatas/32/1742_2.png) [@Martin\_Hatas](https://discuss.elastic.co/u/Martin_Hatas)\ **Post date:** [March 10, 2014, 8:03pm UTC](https://discuss.elastic.co/t/authentication-again/16255/4 "2014-03-10T20:03:32Z")
Thank you very much for answer. I think that elasticsearch-jetty plugin handles only http request, am I right? (REST API requests) I have alrery disable http by _http.enabled: false_ option and I want to secure comunication amog the nodes. For access to the cluster I use JAVA API. For me it´s not clear if elasticsearch-jetty can encrypt this comunication. Dne pondělí, 10. března 2014 18:05:35 UTC+1 Binh Ly napsal(a): > Perhaps you can give this a try: > > [GitHub - sonian/elasticsearch-jetty](https://github.com/sonian/elasticsearch-jetty) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/301cfea2-9ddb-4743-b517-629127e9941c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/301cfea2-9ddb-4743-b517-629127e9941c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![zkidkid](https://avatars.discourse-cdn.com/v4/letter/z/fbc32d/32.png) [@zkidkid](https://discuss.elastic.co/u/zkidkid)\ **Post date:** [March 13, 2014, 4:12pm UTC](https://discuss.elastic.co/t/authentication-again/16255/5 "2014-03-13T16:12:40Z")
Hi Martin, For your situation, I suggest: 1.Disable HTTP & run your ES node only in internal network. 2.Making a middleware to provide a restful service so that other could communicate. 3. Your middleware will listen & use client api (ex: java client) to work with ES cluster & return result back. Regards. On Sunday, March 9, 2014 11:14:15 PM UTC+7, Martin Hátaš wrote: > I know that authentication between nodes (native protocol) is not provided > natively by ES. > But I have 2 aditional questions: > > 1. Do you consider to put this functionality to the roadmap (in the near > future)? > 2. Have anyone solved this issue by some homebrewed solution (e.g. by > wrapping or extending Node/Client class)? > > We really recognize ES as brilliant piece of software for MANY reasons but > we cann´t intergrate it to our product/solutions mainly due to missing > authentication/encryption. > > Thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d28f0d19-3137-497e-8775-3be7f171e960%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d28f0d19-3137-497e-8775-3be7f171e960%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:43am UTC](https://discuss.elastic.co/t/authentication-again/16255/6 "2017-07-06T01:43:25Z")