# Basic X-Pack Licence against cluster

**URL:** <https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962>\
**Category:** Elasticsearch\
**Created:** [May 31, 2018, 3:24am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962 "2018-05-31T03:24:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jithesh\_Pk](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@Jithesh\_Pk](https://discuss.elastic.co/u/Jithesh_Pk)\
**Post date:** [May 31, 2018, 3:24am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962/1 "2018-05-31T03:24:33Z")

</div>

Hi,  
When done basic licence upgrade against a single node, it was a success.

But we getting some warning like below when apply the Basic Licence against a cluster with 3 nodes.

```
{
  "acknowledged" : false,
  "license_status" : "valid",
  "acknowledge" : {
    "message" : "This license update requires acknowledgement. To acknowledge the license, please read the following messages and update the license again, this time with the \"acknowledge=true\" parameter:",
    "watcher" : [
      "Watcher will be disabled"
    ],
    "security" : [
      "The following X-Pack security functionality will be disabled: authentication, authorization, ip filtering, and auditing. Please restart your node after applying the license.",
      "Field and document level access control will be disabled.",
      "Custom realms will be ignored."
    ],
    "monitoring" : [
      "Multi-cluster support is disabled for clusters with [BASIC] license. If you are\nrunning multiple clusters, users won't be able to access the clusters with\n[BASIC] licenses from within a single X-Pack Kibana instance. You will have to deploy a\nseparate and dedicated X-pack Kibana instance for each [BASIC] cluster you wish to monitor.",
      "Automatic index cleanup is locked to 7 days for clusters with [BASIC] license."
    ],
    "graph" : [
      "Graph will be disabled"
    ],
    "ml" : [
      "Machine learning will be disabled"
    ]
  }
}

```

We done the licence upgrade and extended the date by acknowledge as true.

But here is there any issue because of the disabled "X-Pack security functionality" ?

---

<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:** [May 31, 2018, 3:29am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962/2 "2018-05-31T03:29:33Z")

</div>

> [@Jithesh\_Pk](#):
>
> This license update requires acknowledgement. To acknowledge the license, please read the following messages and update the license again, this time with the "acknowledge=true" parameter

Did you do as it mentioned in the response?

---

<div class="post-metadata">

**Author:** ![Jithesh\_Pk](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@Jithesh\_Pk](https://discuss.elastic.co/u/Jithesh_Pk)\
**Post date:** [May 31, 2018, 3:32am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962/3 "2018-05-31T03:32:35Z")

</div>

> [@Jithesh\_Pk](#):
>
> We done the licence upgrade and extended the date by acknowledge as true.
> 
> But here is there any issue because of the disabled "X-Pack security functionality" ?

Yes done and then got the successful response. Also the date extended to one year.  
But our concern, will it make any issue in future because of the disabled security functions like showing in the message  
"The following X-Pack security functionality will be disabled: authentication, authorization, ip filtering, and auditing. Please restart your node after applying the license."

Or after restart will we get this functions ?

---

<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:** [May 31, 2018, 3:33am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962/4 "2018-05-31T03:33:24Z")

</div>

Those features are not part of the Basic license, see [https://www.elastic.co/subscriptions](https://www.elastic.co/subscriptions)

---

<div class="post-metadata">

**Author:** ![Jithesh\_Pk](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@Jithesh\_Pk](https://discuss.elastic.co/u/Jithesh_Pk)\
**Post date:** [May 31, 2018, 3:36am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962/5 "2018-05-31T03:36:55Z")

</div>

Yeah, thanks .

But when we done the basic licence against a single node without cluster, we didn't received these errors and got upgraded in single upgrade command.  
But the same didn't worked against a cluster, so that's why we confused.

---

<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:** [June 28, 2018, 3:37am UTC](https://discuss.elastic.co/t/basic-x-pack-licence-against-cluster/133962/6 "2018-06-28T03:37:04Z")

</div>

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