# Reg: Cluster Privileges for Snapshots - Permission issue

**URL:** https://discuss.elastic.co/t/reg-cluster-privileges-for-snapshots-permission-issue/132228
**Category:** Elasticsearch
**Created:** [May 16, 2018, 11:31pm UTC](https://discuss.elastic.co/t/reg-cluster-privileges-for-snapshots-permission-issue/132228 "2018-05-16T23:31:56Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)
#### Post date: [May 16, 2018, 11:31pm UTC](https://discuss.elastic.co/t/reg-cluster-privileges-for-snapshots-permission-issue/132228/1 "2018-05-16T23:31:56Z")

</div>

We are using Azure Repository Plugin (ES 6.2.1) for snapshotting, and use curator actions for snapshot action. But, the action is error'ing out as below

action [cluster:admin/repository/get] is unauthorized for user  
Error from DEBUG log  
2018-05-16 22:50:48,369 DEBUG elasticsearch log\_request\_fail:110 \< {"error":{"root\_cause":[{"type":"security\_exception","reason":"action [cluster:admin/repository/get] is unauthorized for user [curator]"}],"type":"security\_exception","reason":"action [cluster:admin/repository/get] is unauthorized for user [curator]"},"status":403}

The user that curator uses to perform snapshot has below privileges

{  
"cluster": ["manage"],  
"indices": [  
{  
"names": ["\*"],  
"privileges": ["monitor", "delete\_index"]  
}  
],  
"run\_as": [],  
"metadata": {}  
}

Shouldn't "manage" help in posting snapshot by curator? Giving "all" would be more as it provides restarting capabilities.

Referring to documentation  
[https://www.elastic.co/guide/en/x-pack/current/security-privileges.html](https://www.elastic.co/guide/en/x-pack/current/security-privileges.html)

---

<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: [May 17, 2018, 2:37am UTC](https://discuss.elastic.co/t/reg-cluster-privileges-for-snapshots-permission-issue/132228/2 "2018-05-17T02:37:57Z")

</div>

> [@Karthik\_Ramachandran](#):
>
> Shouldn't "manage" help in posting snapshot by curator?

`manage` should do what you need. Are you _sure_ that your curator used is configured correctly?

The [Authenticate API](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/security-api-authenticate.html) can help diagnose which roles a user has.

> [@Karthik\_Ramachandran](#):
>
> Giving "all" would be more as it provides restarting capabilities.

The documentation is not very clear on this point, but `manage` can do everything that `all` can do, _except_ manage security.

---

<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 14, 2018, 2:37am UTC](https://discuss.elastic.co/t/reg-cluster-privileges-for-snapshots-permission-issue/132228/3 "2018-06-14T02:37:58Z")

</div>

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