# Current license is non-compliant even after installing licence

**URL:** <https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164>\
**Category:** Kibana\
**Created:** [March 10, 2017, 3:53pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164 "2017-03-10T15:53:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![robomotic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robomotic/32/16256_2.png) [@robomotic](https://discuss.elastic.co/u/robomotic)\
**Post date:** [March 10, 2017, 3:53pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164/1 "2017-03-10T15:53:12Z")

</div>

I need some serious help with this as I am clueless.  
Some day ago my Kibana dashboard was not requiring authentication anymore on my public facing IP.  
I went to check logs and discovered that XPAck requires a licence after 30 days.  
I have installed the licence on the ElasticSearch server where Kibana connects successfully and even received a confirmation email.  
However my Kibana dashboard is still unprotected and I can still see this error:

```
"type": "security_exception",
"reason": "current license is non-compliant for [security]",
"license.expired.feature": "security"

```

Is there something else I have to do on Kibana config to re-enable user authentication.

I have checked kibana.yml and nothing related to XPack is disabled.

I don't really know what's going on .  
Cheers.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 10, 2017, 4:43pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164/2 "2017-03-10T16:43:17Z")

</div>

Are you using a basic license? See [https://www.elastic.co/subscriptions](https://www.elastic.co/subscriptions)

---

<div class="post-metadata">

**Author:** ![robomotic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robomotic/32/16256_2.png) [@robomotic](https://discuss.elastic.co/u/robomotic)\
**Post date:** [March 10, 2017, 4:55pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164/3 "2017-03-10T16:55:53Z")

</div>

Yes I double checked this is what I received on my email confirmation:

Thank you for using the Elastic Stack and registering for your free Basic license! This license expires on March 9, 2018.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 10, 2017, 4:56pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164/4 "2017-03-10T16:56:38Z")

</div>

The Security functionality is not available on that level, check the link for more.

---

<div class="post-metadata">

**Author:** ![robomotic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robomotic/32/16256_2.png) [@robomotic](https://discuss.elastic.co/u/robomotic)\
**Post date:** [March 10, 2017, 4:58pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164/5 "2017-03-10T16:58:35Z")

</div>

Ouch I didn't realize I am guessing is under the :Native authentication, encrypted communications ?

---

<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:** [April 7, 2017, 4:58pm UTC](https://discuss.elastic.co/t/current-license-is-non-compliant-even-after-installing-licence/78164/6 "2017-04-07T16:58:42Z")

</div>

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