# Protect Elasticsearch using Oauth

**URL:** <https://discuss.elastic.co/t/protect-elasticsearch-using-oauth/73710>\
**Category:** Elasticsearch\
**Created:** [February 2, 2017, 3:34pm UTC](https://discuss.elastic.co/t/protect-elasticsearch-using-oauth/73710 "2017-02-02T15:34:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jorgenb](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@jorgenb](https://discuss.elastic.co/u/jorgenb)\
**Post date:** [February 2, 2017, 3:34pm UTC](https://discuss.elastic.co/t/protect-elasticsearch-using-oauth/73710/1 "2017-02-02T15:34:28Z")

</div>

I, nor my users, can afford X-pack og similar commercial alternatives to protect Elasticsearch. I have several use cases that require me to put Elasticsearch on the Internet and as such I have started a little project that will allow you to protect individual Elasticsearch indices using a combination of Oath 2.0 Personal Access Tokens and JSON Web Tokens.

In a nutshell:

- Provide the use of Personal Access Tokens to protect Elasticsearch. Frees you from having to manage Basic Auth at the server level.
- JSON Api for managing indices and tokens.
- Also, a self service frontend GUI allowing users to set create their own indices and attach tokens to these.

For more information please see [https://github.com/jorgenb/elasticshield](https://github.com/jorgenb/elasticshield). I realise that it does not solve anything new but I hope that with time and feedback I will be able to grow it to solution that can benefit many.

---

<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:** [March 2, 2017, 3:34pm UTC](https://discuss.elastic.co/t/protect-elasticsearch-using-oauth/73710/2 "2017-03-02T15:34:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.