elastic / elasticsearch

Free and Open Source, Distributed, RESTful Search Engine
https://www.elastic.co/products/elasticsearch
Other
69.73k stars 24.68k forks source link

[Security] Add hostname/FQDN documentation for filtering #29945

Open elasticmachine opened 7 years ago

elasticmachine commented 7 years ago

Original comment by @gmoskovicz:

See LINK REDACTED

xpack.security.transport.filter.allow seems to be needed the FQDN and no hostnames, regardless that the hostnames are resolving internally in each node. If you use the FQDN it will work. I tried to look around the repository but we don't have tests for this neither the documentation explicitly mentions that we need FQDN to work?

CC @jaymode

elasticmachine commented 7 years ago

Original comment by @jaymode:

This is pretty hard to test since you would need to setup DNS or some other way to resolve names. I think doc wise we can add something to that effect.

elasticmachine commented 7 years ago

Original comment by @gmoskovicz:

@jaymode docs will be a good idea. Do you know if FQDN is required, or this should work with hostnames?

elasticmachine commented 7 years ago

Original comment by @jaymode:

It is dependent on what reverse DNS resolves IIRC

elasticmachine commented 7 years ago

Original comment by @gmoskovicz:

If the hostname is setinside the allow filter, it doesn't work. If the FQDN or IP addressis set, it does work. So i think that FQDN is required. Hence my request 🙂

jrodewig commented 4 years ago

[docs issue triage]