OpenSearch

History

Jay Modi d44ba28d27 security: always create the IPFilter in a node When running as a node, we check the `xpack.security.transport.filter.enabled` setting to see if we should create the IPFilter but this check is not really correct. The HTTP filter could be enabled or a profile filter could be enabled so there are times when we may not be filtering connections when we should. Additionally, since we do not bind the IPFilter to a null provider, Guice will try to create one during startup to inject into the security transport. This results in an exception and startup fails. This change always creates the IPFilter when running as a node. This IPFilter has its own settings and logic to determine whether it should be filtering on a given network transport. Closes elastic/elasticsearch#3592 Original commit: elastic/x-pack-elasticsearch@95c25651c4		2016-09-23 10:12:24 -04:00
..
bin/x-pack	security: fix typo is syskeygen script	2016-09-12 12:26:14 -04:00
config/x-pack	Complete Elasticsearch logger names	2016-09-13 22:47:10 -04:00
src	security: always create the IPFilter in a node	2016-09-23 10:12:24 -04:00
README.asciidoc	security: remove use of shield in files and directory names	2016-06-20 10:26:10 -04:00
TESTING.asciidoc	security: remove use of shield in files and directory names	2016-06-20 10:26:10 -04:00
test-signatures.txt	security: remove use of shield in files and directory names	2016-06-20 10:26:10 -04:00

README.asciidoc

= Elasticsearch Security Plugin

This plugins adds security features to elasticsearch

You can build the plugin with `mvn package`.

The documentation is put in the `docs/` directory.