# Protect the enterprise search login page

**URL:** <https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319>\
**Category:** Elastic Search\
**Created:** [January 27, 2021, 7:00am UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319 "2021-01-27T07:00:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tonytsangln](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tonytsangln/32/81286_2.png) [@tonytsangln](https://discuss.elastic.co/u/tonytsangln)\
**Post date:** [January 27, 2021, 7:00am UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/1 "2021-01-27T07:00:46Z")

</div>

Hi all,

I am currently setting up the enterprise search free version in my server, I would like to ask is there any way can help to protect the login page? E.g only limit some IP can access the /login path.

Thank you,  
Tony

---

<div class="post-metadata">

**Author:** ![david.harsha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/david.harsha/32/48003_2.png) [@david.harsha](https://discuss.elastic.co/u/david.harsha)\
**Post date:** [January 27, 2021, 9:36pm UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/2 "2021-01-27T21:36:58Z")

</div>

Hi @tonytsangln, that's not currently possible in Enterprise Search. I would recommend putting Enterprise Search behind a proxy to add access restrictions.

---

<div class="post-metadata">

**Author:** ![tonytsangln](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tonytsangln/32/81286_2.png) [@tonytsangln](https://discuss.elastic.co/u/tonytsangln)\
**Post date:** [January 28, 2021, 5:59am UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/3 "2021-01-28T05:59:07Z")

</div>

> [@david.harsha](#):
>
> restrictions

Hi David,  
Thank you for your reply, may I know is there any document can let me know more details?

I set the enterprise search to localhost, and use the nginx reverse proxy to protect, but it seems enterprise search many request (e.g Ajax) still requesting the localhost when I access the login page via the reverse proxy. Is there any setting that I need to apply in enterprise-search config?

Here is my url setting in enterprise search

> ent\_search.external\_url: [http://127.0.0.1:3002](http://127.0.0.1:3002)  
> ent\_search.listen\_host: 127.0.0.1  
> ent\_search.listen\_port: 3002

Thank you  
Tony

---

<div class="post-metadata">

**Author:** ![david.harsha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/david.harsha/32/48003_2.png) [@david.harsha](https://discuss.elastic.co/u/david.harsha)\
**Post date:** [January 28, 2021, 8:19pm UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/4 "2021-01-28T20:19:18Z")

</div>

You'll need to set `ent_search.external_url` to whatever host the reverse proxy is exposing.

---

<div class="post-metadata">

**Author:** ![tonytsangln](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tonytsangln/32/81286_2.png) [@tonytsangln](https://discuss.elastic.co/u/tonytsangln)\
**Post date:** [January 29, 2021, 8:09am UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/5 "2021-01-29T08:09:09Z")

</div>

Thank you, is it correct if my reverse proxy is expose to [http://domain1:3003](http://domain1:3003)?

> ent\_search.external\_url: [http://domain1:3002](http://domain1:3002)  
> ent\_search.listen\_host: 127.0.0.1  
> ent\_search.listen\_port: 3002

---

<div class="post-metadata">

**Author:** ![david.harsha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/david.harsha/32/48003_2.png) [@david.harsha](https://discuss.elastic.co/u/david.harsha)\
**Post date:** [January 29, 2021, 8:14pm UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/6 "2021-01-29T20:14:30Z")

</div>

`external_url` should use the exposed port as well: `ent_search.external_url: http://domain1:3003`

---

<div class="post-metadata">

**Author:** ![tonytsangln](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tonytsangln/32/81286_2.png) [@tonytsangln](https://discuss.elastic.co/u/tonytsangln)\
**Post date:** [January 31, 2021, 9:28am UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/7 "2021-01-31T09:28:16Z")

</div>

Thank you, it works now.

---

<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:** [November 4, 2022, 8:22am UTC](https://discuss.elastic.co/t/protect-the-enterprise-search-login-page/262319/8 "2022-11-04T08:22:36Z")

</div>

Closed on November 4, 2022, 8:22am UTC


