Authentication & Authorization

[karussell]

There are several points regarding security:

1. make sure that one can authenticate into ElasticSearch
2. make sure that sensitive data is encrypted when sending over the network and also between nodes
3. make sure that an authenticated user can see and change only his own 'things' (indices, data, node info)

Point 1 and 2 are already requested in issue #664. What I'm after is point 3. I wanted to ask you how you would implement point 1 and 3 (point 2 can be handled by someone else ;))

I've thought one could simply store user and password (as updateable settings) while creating an index. And when searching or indexing one needs to provide the user and pw. To keep it simple there is only one admin user which has access to the node and cluster health information etc. All other users are normal user and can only perform "CRUD" actions for indices and its data.

Now my problem is that when I intercept every request to authenticate & authorize I would have to touch over 10 Request classes implementing ActionRequest.validate() for the transport client. Also there are no settings stored for those Requests.

Or how would you implement this?

And then for the rest client it looks a bit simpler because the settings are already in the request and I could then change the BaseRestHandler only to implement a validation within handleRequest. Is this correct?

Or is there a simpler or more powerful scenarios to implement my feature requests?

[starfishmod]

+1 for this. Would great to be able to configure the access to various API's on a per index level

[bryangreen]

+1

[asafdav2]

+1

[tarunjangra]

Absolutely +1. Really waiting for these features. Do we have any progresses on any of above?

[karussell]

see https://github.com/sonian/elasticsearch-jetty

[tarunjangra]

@karussell: Cool feature. Thank you for that.

[pulkitsinghal]

For those using the jetty plugin:
https://github.com/sonian/elasticsearch-jetty

You can also utilize the Chef cookbook to speed-up your AWS deployments:
https://github.com/pulkitsinghal/cookbook-elasticsearch

[pannous]

+1

[thejohnfreeman]

OP's needs may be addressed, but the general issue remains. The Java API communicates through the transport module which I'm guessing implements some custom protocol, unencrypted, over TCP.

Is there a setting to disallow Java API clients? That is, can a node disallow TCP connections from outside the cluster?

Is there a setting to encrypt network traffic among the cluster?