# How can i configure hdfs repository with kerberos in a security hdfs cluster?

**URL:** <https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189>\
**Category:** Elasticsearch\
**Tags:** es-hadoop\
**Created:** [February 7, 2017, 9:18am UTC](https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189 "2017-02-07T09:18:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xy\_xin](https://avatars.discourse-cdn.com/v4/letter/x/ba9def/32.png) [@xy\_xin](https://discuss.elastic.co/u/xy_xin)\
**Post date:** [February 7, 2017, 9:18am UTC](https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189/1 "2017-02-07T09:18:04Z")

</div>

Here is my settings, but it doesn't work (seems the same with [repository-hdfs no work with Kerberos authenticate hdfs · Issue #921 · elastic/elasticsearch-hadoop · GitHub](https://github.com/elastic/elasticsearch-hadoop/issues/921)).

> {  
> "type": "hdfs",  
> "settings": {  
> "path": "/user/me/es\_repo",  
> "compress": "true",  
> "uri": "hdfs://namenode:8020",  
> "max\_snapshot\_bytes\_per\_sec": "500mb",  
> "max\_restore\_bytes\_per\_sec": "500mb",  
> "conf\_location": "/path/to/my/core-site.xml,/path/to/my/hdfs-site.xml",  
> "user\_keytab": "/data/keytab/user.keytab"  
> }  
> }

below is the error,

> {  
> "error": {  
> "root\_cause": [  
> {  
> "type": "generation\_exception",  
> "reason": "Cannot create HDFS repository for uri [hdfs://100.106.75.147:25000]"  
> }  
> ],  
> "type": "repository\_exception",  
> "reason": "[hdfs\_repository] failed to create repository",  
> "caused\_by": {  
> "type": "generation\_exception",  
> "reason": "Cannot create HDFS repository for uri [hdfs://100.106.75.147:25000]",  
> "caused\_by": {  
> "type": "i\_o\_exception",  
> "reason": "SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS]",  
> "caused\_by": {  
> "type": "i\_o\_exception",  
> "reason": "SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS]"  
> }  
> }  
> }  
> },  
> "status": 500  
> }

---

<div class="post-metadata">

**Author:** ![xy\_xin](https://avatars.discourse-cdn.com/v4/letter/x/ba9def/32.png) [@xy\_xin](https://discuss.elastic.co/u/xy_xin)\
**Post date:** [February 7, 2017, 9:19am UTC](https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189/2 "2017-02-07T09:19:38Z")

</div>

i'm using elasticsearch-5.1.1.

---

<div class="post-metadata">

**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\
**Post date:** [February 14, 2017, 8:27pm UTC](https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189/3 "2017-02-14T20:27:05Z")

</div>

@xy_xin Kerberos authentication for the HDFS Repository Snapshot plugin does not function correctly in 5.x at the moment. There is currently an effort to re-add this functionality so that it may function well with the internal security manager.

---

<div class="post-metadata">

**Author:** ![xy\_xin](https://avatars.discourse-cdn.com/v4/letter/x/ba9def/32.png) [@xy\_xin](https://discuss.elastic.co/u/xy_xin)\
**Post date:** [February 15, 2017, 1:04am UTC](https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189/4 "2017-02-15T01:04:38Z")

</div>

Thanks for your information @james.baiera.

---

<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 15, 2017, 1:04am UTC](https://discuss.elastic.co/t/how-can-i-configure-hdfs-repository-with-kerberos-in-a-security-hdfs-cluster/74189/5 "2017-03-15T01:04:47Z")

</div>

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