# No permissions for user | Security Exception

**URL:** <https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [June 8, 2023, 5:33am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499 "2023-06-08T05:33:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faisal\_Umer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faisal_umer/32/105463_2.png) [@Faisal\_Umer](https://discuss.elastic.co/u/Faisal_Umer)\
**Post date:** [June 8, 2023, 5:33am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/1 "2023-06-08T05:33:47Z")

</div>

I have to delay the shards assignment after a failure and running this command for that

```auto

PUT _all/_settings
{
  "settings": {
    "index.unassigned.node_left.delayed_timeout": "5m"
  }
}

```

Getting the following error while running this

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "security_exception",
        "reason" : "no permissions for [] and User [name=<my-email-address>, backend_roles=[admin], requestedTenant=null]"
      }
    ],
    "type" : "security_exception",
    "reason" : "no permissions for [] and User [name=<my-email-address>, backend_roles=[admin], requestedTenant=null]"
  },
  "status" : 403
}

```

After a bit of research, I found a similar thread  
[https://forum.opensearch.org/t/no-permission-for-user-tenant-permission-error/1230](https://forum.opensearch.org/t/no-permission-for-user-tenant-permission-error/1230)

I tried to run the command from inside the Kibana EC2 instance along with certificates and got the following error

```auto
error reading X.509 key or certificate file: Error in parsing when sending certificate in Curl Request

```

This StackOverflow thread suggests to create new certificates  
[https://stackoverflow.com/questions/50390689/error-reading-x-509-key-or-certificate-file-error-in-parsing-when-sending-certi](https://stackoverflow.com/questions/50390689/error-reading-x-509-key-or-certificate-file-error-in-parsing-when-sending-certi)

I have two questions

1. Can I apply the node delay settings some other way?
2. If not, should I create new certificates? Will it cause any issues in the existing setup?

---

<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 8, 2023, 5:33am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/2 "2023-06-08T05:33:47Z")

</div>

OpenSearch/OpenDistro are AWS run products and differ from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

---

<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:** [June 8, 2023, 10:34pm UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/3 "2023-06-08T22:34:00Z")

</div>

Are you using Elasticsearch or opensearch?

---

<div class="post-metadata">

**Author:** ![Faisal\_Umer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faisal_umer/32/105463_2.png) [@Faisal\_Umer](https://discuss.elastic.co/u/Faisal_Umer)\
**Post date:** [June 9, 2023, 5:17am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/4 "2023-06-09T05:17:04Z")

</div>

We are using self-managed Elasticsearch 7.8.0 hosted on AWS EC2 instances.

---

<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:** [June 13, 2023, 12:23am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/5 "2023-06-13T00:23:40Z")

</div>

OK, please note that version is [EOL](https://www.elastic.co/support/eol) and no longer supported so you should be looking to upgrade as a matter of urgency.

What user are you trying to authenticate as?

---

<div class="post-metadata">

**Author:** ![Faisal\_Umer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faisal_umer/32/105463_2.png) [@Faisal\_Umer](https://discuss.elastic.co/u/Faisal_Umer)\
**Post date:** [June 14, 2023, 6:28am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/6 "2023-06-14T06:28:53Z")

</div>

Yeah, we are planning an upgrade, and it might take some time.

On dev tools, I tried to run it as my own user with admin permissions assigned. On EC2 instances, I ran the curl command as the root user.

---

<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:** [June 20, 2023, 8:52am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/7 "2023-06-20T08:52:58Z")

</div>

> [@Faisal\_Umer](#):
>
> I ran the curl command as the root user.

What user did you auth to Elasticsearch with though?

---

<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:** [July 18, 2023, 8:53am UTC](https://discuss.elastic.co/t/no-permissions-for-user-security-exception/335499/8 "2023-07-18T08:53:00Z")

</div>

Closed on July 18, 2023, 8:53am UTC

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