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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d28f0d19-3137-497e-8775-3be7f171e960%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
