# CCR user permission issue. \[indices:admin/seq\_no/renew\_retention\_lease\] is unauthorized for user \[ccr\_user\]

**URL:** <https://discuss.elastic.co/t/ccr-user-permission-issue-indices-admin-seq-no-renew-retention-lease-is-unauthorized-for-user-ccr-user/276677>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security, ccr-cross-cluster-replication\
**Created:** [June 22, 2021, 4:19pm UTC](https://discuss.elastic.co/t/ccr-user-permission-issue-indices-admin-seq-no-renew-retention-lease-is-unauthorized-for-user-ccr-user/276677 "2021-06-22T16:19:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [June 23, 2021, 12:01am UTC](https://discuss.elastic.co/t/ccr-user-permission-issue-indices-admin-seq-no-renew-retention-lease-is-unauthorized-for-user-ccr-user/276677/3 "2021-06-23T00:01:25Z")

</div>

Yes it is a bug and it is not fixed yet. For now you can work around this by either grant `manage` privilege or explicitly add the action name for the remote index, e.g.:

```auto
ccr_leader:
    cluster:
      - read_ccr
      - monitor
    indices:
      - names: '*'
        privileges:
          - read
          - manage

```

---

_[View the full topic](https://discuss.elastic.co/t/ccr-user-permission-issue-indices-admin-seq-no-renew-retention-lease-is-unauthorized-for-user-ccr-user/276677)._