# Upgrade Elastic and Kibana from 7.17 to 8.7 - S

**URL:** https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036
**Category:** Kibana
**Tags:** elastic-stack-security
**Created:** [May 10, 2023, 7:43am UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036 "2023-05-10T07:43:06Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![charlot\_Attard](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@charlot\_Attard](https://discuss.elastic.co/u/charlot_Attard)
#### Post date: [May 10, 2023, 7:43am UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/1 "2023-05-10T07:43:06Z")

</div>

Hello,

We are in the process of migrating our Elasticsearch and Kibana from 7.17 to 8.7. We are facing an issue where after upgrading Elasticsearch works out fine but when starting Kibana we are seeing these errors.

"Action failed with 'security\_exception Root cause security\_exception action [indices: adamin/create] is unathorized for user [username] with effective roles superuser on restricted indices [.kibana\_8.71\_001] This action is granted by the index priviliges [create\_index,manage,alll]' Retrying attempt "

Any idea what can be the issue ? Thankyou

---

<div class="post-metadata">

### Author: ![cperzrt10](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cperzrt10/32/116152_2.png) [@cperzrt10](https://discuss.elastic.co/u/cperzrt10)
#### Post date: [May 10, 2023, 3:11pm UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/2 "2023-05-10T15:11:48Z")

</div>

Maybe the user that are writing not have the proper privileges?

---

<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 11, 2023, 12:02am UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/3 "2023-05-11T00:02:09Z")

</div>

> [@charlot\_Attard](#):
>
> unathorized for user [username]

Have you looked at the roles of this user to make sure they have the requirements;

> [@charlot\_Attard](#):
>
> action is granted by the index priviliges [create\_index,manage,alll

---

<div class="post-metadata">

### Author: ![charlot\_Attard](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@charlot\_Attard](https://discuss.elastic.co/u/charlot_Attard)
#### Post date: [May 11, 2023, 7:44am UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/4 "2023-05-11T07:44:34Z")

</div>

User has the role as superuser, from what I found out these seem to be protected indexes and its not possible to have these permissions on them. What way can I grant the user "elastic" authorization on those indices ?

---

<div class="post-metadata">

### Author: ![Yang\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yang_wang/32/48857_2.png) [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)
#### Post date: [May 12, 2023, 1:53am UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/5 "2023-05-12T01:53:28Z")

</div>

Superuser no longer has write permission to system indices (.kibana is one of them) in 8.x. For running kibana, the recommendation is to use either the dedicate `kibana_system` user or the `elastic/kibana` service account instead of the `elastic` user. These can be configured with either `elasticsearch.username` and `elasticsearch.password` or `elasticsearch.serviceAccountToken`.

---

<div class="post-metadata">

### Author: ![charlot\_Attard](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@charlot\_Attard](https://discuss.elastic.co/u/charlot_Attard)
#### Post date: [May 12, 2023, 1:15pm UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/6 "2023-05-12T13:15:39Z")

</div>

> [@Yang\_Wang](#):
>
> serviceAccountToken

Thanks a lot for your reply @Yang_Wang When I specified elastic.username and elastic.password for kibana\_system. KIbana application still tried to access elastic via a user called "elasticdeploy" although this user is not specified in kibana.yml

---

<div class="post-metadata">

### Author: ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)
#### Post date: [May 12, 2023, 2:32pm UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/7 "2023-05-12T14:32:53Z")

</div>

try this. I remember I had same issue as well

use kibana\_system inbuilt user in kibana.yml for example.

```auto
# less /etc/kibana/kibana.yml |grep kibana
elasticsearch.username: "kibana_system"
elasticsearch.password: "kibana_password"

```

if you do not know the password of this user setup like this

`/usr/share/elasticsearch/bin/elasticsearch-reset-password -i -u kibana_system`

---

<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 9, 2023, 2:33pm UTC](https://discuss.elastic.co/t/upgrade-elastic-and-kibana-from-7-17-to-8-7-s/333036/8 "2023-06-09T14:33:29Z")

</div>

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