# Kibana 6.1-Login is currently disabled. Administrators should consult the Kibana logs for more details

**URL:** https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106
**Category:** Kibana
**Created:** [December 16, 2017, 9:20pm UTC](https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106 "2017-12-16T21:20:46Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Francesca\_P](https://avatars.discourse-cdn.com/v4/letter/f/7feea3/32.png) [@Francesca\_P](https://discuss.elastic.co/u/Francesca_P)
#### Post date: [December 16, 2017, 9:20pm UTC](https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106/1 "2017-12-16T21:20:46Z")

</div>

Hi everyone,  
I installed for the first time the stack elk (version 6.1.0) on windows following the guide.

After running the x-pack installation I added the following line in the kibana.yml and elasticsearch.yml file: # xpack.security.enabled: false.  
But when I open kibana the login form is disabled:  
 ![Cattura](https://us1.discourse-cdn.com/elastic/original/3X/c/a/ca26daad05583c2fe5e2b0719f657b77b41afcea.PNG)

and I get the following message:

```
  log [21:05:42.568] [warning][security] Generating a random key for xpack.sec
urity.encryptionKey. To prevent sessions from being invalidated on restart, plea
se set xpack.security.encryptionKey in kibana.yml
  log [21:05:42.574] [warning][security] Session cookies will be transmitted o
ver insecure connections. This is not recommended.
  log [21:05:42.606] [error][status][plugin:searchprofiler@6.1.0] Status chang
ed from uninitialized to red - [security_exception] missing authentication token
 for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"sec
urity\" charset=\"UTF-8\"" } }
  log [21:05:42.613] [error][status][plugin:ml@6.1.0] Status changed from unin
itialized to red - [security_exception] missing authentication token for REST re
quest [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" char
set=\"UTF-8\"" } }
  log [21:05:42.698] [error][status][plugin:tilemap@6.1.0] Status changed from
 uninitialized to red - [security_exception] missing authentication token for RE
ST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\"
 charset=\"UTF-8\"" } }
  log [21:05:42.704] [error][status][plugin:watcher@6.1.0] Status changed from
 uninitialized to red - [security_exception] missing authentication token for RE
ST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\"
 charset=\"UTF-8\"" } }
  log [21:05:42.731] [info][status][plugin:grokdebugger@6.1.0] Status changed
from uninitialized to green - Ready
  log [21:05:42.740] [info][status][plugin:dashboard_mode@6.1.0] Status change
d from uninitialized to green - Ready
  log [21:05:42.744] [error][status][plugin:logstash@6.1.0] Status changed fro
m uninitialized to red - [security_exception] missing authentication token for R
EST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\
" charset=\"UTF-8\"" } }
  log [21:05:42.778] [info][status][plugin:apm@6.1.0] Status changed from unin
itialized to green - Ready
  log [21:05:42.782] [info][status][plugin:license_management@6.1.0] Status ch
anged from uninitialized to green - Ready
  log [21:05:42.791] [info][status][plugin:console@6.1.0] Status changed from
uninitialized to green - Ready
  log [21:05:42.806] [info][status][plugin:metrics@6.1.0] Status changed from
uninitialized to green - Ready
  log [21:05:43.887] [info][status][plugin:timelion@6.1.0] Status changed from
 uninitialized to green - Ready
  log [21:05:43.893] [info][listening] Server running at http://localhost:5601

  log [21:05:48.648] [warning][license][xpack] License information from the X-
Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [se
curity_exception] missing authentication token for REST request [/_xpack], with
{ header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } ::
{"path":"/_xpack","statusCode":401,"response":"{\"error\":{\"root_cause\":[{\"ty
pe\":\"security_exception\",\"reason\":\"missing authentication token for REST r
equest [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\
\" charset=\\\"UTF-8\\\"\"}}],\"type\":\"security_exception\",\"reason\":\"missi
ng authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authentic
ate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}},\"status\":401}",
"wwwAuthenticateDirective":"Basic realm=\"security\" charset=\"UTF-8\""}

```

can someone help me?

I would like to disable authentication via x-pack. What can I do?

---

<div class="post-metadata">

### Author: ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)
#### Post date: [December 17, 2017, 9:20pm UTC](https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106/2 "2017-12-17T21:20:43Z")

</div>

It appears that authentication is still enabled on you Elasticsearch cluster.

Did you restart the cluster after you changed the configuration?

What does this command produce?

```auto
curl 'http://localhost:9200/'

```

---

<div class="post-metadata">

### Author: ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)
#### Post date: [December 17, 2017, 9:23pm UTC](https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106/3 "2017-12-17T21:23:47Z")

</div>

> [@Francesca\_P](#):
>
> added the following line in the kibana.yml and elasticsearch.yml file: # xpack.security.enabled: false.

Did you include that `#` in the configuration file?  
That makes the whole line into a comment, so it achieves nothing. The config should be

```auto
xpack.security.enabled: false

```

---

<div class="post-metadata">

### Author: ![Francesca\_P](https://avatars.discourse-cdn.com/v4/letter/f/7feea3/32.png) [@Francesca\_P](https://discuss.elastic.co/u/Francesca_P)
#### Post date: [December 18, 2017, 11:16am UTC](https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106/4 "2017-12-18T11:16:20Z")

</div>

Hi Tim,  
I forgot to remove # in the kibana.yml file, I removed it and after restarting the cluster, everything works correctly.

thank you so much

---

<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: [January 15, 2018, 11:16am UTC](https://discuss.elastic.co/t/kibana-6-1-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/112106/5 "2018-01-15T11:16:35Z")

</div>

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