# Integrate Elastic Search Server with Apache or IBM HttpServer

**URL:** <https://discuss.elastic.co/t/integrate-elastic-search-server-with-apache-or-ibm-httpserver/1875>\
**Category:** Elasticsearch\
**Created:** [June 3, 2015, 9:30pm UTC](https://discuss.elastic.co/t/integrate-elastic-search-server-with-apache-or-ibm-httpserver/1875 "2015-06-03T21:30:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![satish](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@satish](https://discuss.elastic.co/u/satish)\
**Post date:** [June 3, 2015, 9:30pm UTC](https://discuss.elastic.co/t/integrate-elastic-search-server-with-apache-or-ibm-httpserver/1875/1 "2015-06-03T21:30:22Z")

</div>

Hi

Our current Deployment plan is to use single Elastic Search integrating with Smart Client  
I want to route all the calls to Elastic Search 9200 port to be intercepted by Siteminder by installing Webagent , basically to protect elastic search indices with unauthorised access  
Appreciate any help with regards this configuration or best ways to protect the elastic search.

---

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [June 6, 2015, 2:47pm UTC](https://discuss.elastic.co/t/integrate-elastic-search-server-with-apache-or-ibm-httpserver/1875/2 "2015-06-06T14:47:58Z")

</div>

firewall the cluster too and make sure elasticsearch instance not run as root.

---

<div class="post-metadata">

**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, 12:09am UTC](https://discuss.elastic.co/t/integrate-elastic-search-server-with-apache-or-ibm-httpserver/1875/3 "2017-07-06T00:09:12Z")

</div>

Closed on July 6, 2017, 12:09am UTC


