# No permissions for \[indices:data/read/msearch\] & \[indices:data/read/scroll\]

**URL:** <https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391>\
**Category:** Security\
**Created:** [November 5, 2026, 4:00am UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391 "2026-11-05T04:00:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![pavani](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@pavani](https://forum.opensearch.org/u/pavani)\
**Post date:** [November 5, 2026, 4:00am UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/1 "2026-11-05T04:00:12Z")

</div>

**Versions** : OpenSearch 3.9.0

**Describe the issue** : While upgrading from 3.4.0 of OpenSearch to 3.9.0 OpenSearch I’m seeing these error logs

{“extra\_data”:{“class”:“o.o.s.p.a.l.PrivilegesEvaluatorImpl”},“message”:“No cluster-level perm match for User [name=abc, backend\_roles=[], requestedTenant=null] Resolved [aliases=[], allIndices=[jaeger-span-2026-10-27, jaeger-span-2026-10-26, jaeger-span-2026-10-25], types=[\*], originalRequested=[jaeger-span-2026-10-27, jaeger-span-2026-10-26, jaeger-span-2026-10-25], remoteIndices=[]] [Action [indices:data/read/msearch]] [RolesChecked [dst\_query, Dst-Query-role]]. No permissions for [indices: data/read/msearch]”

No cluster-level perm match for User [name=xyz, backend\_roles=[], requestedTenant=null] Resolved [aliases=[\*], allIndices=[\*], types=[\*], originalRequested=[\*], remoteIndices=[]] [Action [indices:data/read/scroll]] [RolesChecked [OSS-DDC-role]]. No permissions for [indices: data/read/scroll]

**Configuration** : The role/rolemapping configurations remained unchanged during the upgrade. However, the same configuration that worked before the upgrade started resulting in the above authorization errors afterward. I’m sharing the configuration as well:

roles:

```auto
        - name: "Dst-Query-role"
          reserved: false
          description: "Role for DST Query client name management"
          cluster_permissions:
            - "cluster:monitor/nodes/stats"
            - "indices:admin/index_template/put"
            - "cluster:monitor/main"
            - "cluster:monitor/state"
            - "cluster:monitor/nodes/info"
            - "cluster:monitor/health"
          index_permissions:
            - index_patterns:
                - "jaeger-*"
              allowed_actions:
                - "indices:data/read/search"
        - name: "Dst-Collector-role"
          reserved: false
          description: "Role for DST Collector client name management"
          cluster_permissions:
            - "cluster:monitor/main"
            - "cluster:monitor/state"
            - "cluster:monitor/health"
            - "cluster:monitor/nodes/info"
            - "indices:admin/template/put"
            - "cluster:monitor/nodes/stats"
            - "indices:admin/index_template/put"
          index_permissions:
            - index_patterns:
                - ""
              allowed_actions:
                - "indices:data/write/index"
                - "indices:data/write/bulk[s]"
                - "indices:admin/create"
                - "indices:admin/mapping/put"
        - name: "OSS-DDC-role"
          reserved: false
          description: "Role for OSS-DDC client name management"
          cluster_permissions:
            - "cluster:monitor/main"
            - "cluster:monitor/nodes/stats"
            - "cluster:monitor/state"
            - "cluster:monitor/health"
          index_permissions:
            - index_patterns:
                - "*"
              allowed_actions:
                - "indices:data/read/search"
                - "indices:monitor/settings/get"
                - "indices:monitor/stats"

```

rolesMapping:

```auto
        - name: "Dst-Query-role"
          description: "Map user abc to role Dst-Query-role"
          reserved: false
          users:
            - "abc"
        - name: "Dst-Collector-role"
          description: "Map user mnp to role Dst-Collector-role"
          reserved: false
          users:
            - "mnp"
        - name: "OSS-DDC-role"
          description: "Map user xyz to role OSS-DDC-role"
          reserved: false
          users:
            - "xyz"

```

Any idea on why these authorization errors was coming after upgrade with the same configuration, and I couldn’t find anything in the breaking changes as well?

---

<div class="post-metadata">

**Author:** ![rachelwilson](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rachelwilson](https://forum.opensearch.org/u/rachelwilson)\
**Post date:** [November 9, 2026, 12:08pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/2 "2026-11-09T12:08:20Z")

</div>

your roles only grant the plain search action, and msearch and scroll are separate actions in the security plugin. add indices:data/read/msearch to the Dst-Query role and indices:data/read/scroll to the OSS-DDC one, same index patterns, then re-apply the config (i wrote up the longer version here if it helps: [https://vectle.com/skills/skl\_hM9UZ4KlNZ9qGYhqq80Oyw](https://vectle.com/skills/skl_hM9UZ4KlNZ9qGYhqq80Oyw) ). the RolesChecked list in the error is the tell for which role to edit.

---

<div class="post-metadata">

**Author:** ![Yanlin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/yanlin/32/10286_2.png) [@Yanlin](https://forum.opensearch.org/u/Yanlin)\
**Post date:** [November 10, 2026, 3:33pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/3 "2026-11-10T15:33:10Z")

</div>

Hi @pavani,

Could you clarify what operation triggers these permission errors after the upgrade? Are you querying the indices through the REST API or using OpenSearch Dashboards? If possible, could you share the exact API request or the steps to reproduce the issue?

Could you also share the output of the following API when authenticated as one of the affected users?

```auto
GET /_plugins/_security/authinfo

```

Please redact any sensitive information before sharing.

Thanks!

---

<div class="post-metadata">

**Author:** ![pavani](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@pavani](https://forum.opensearch.org/u/pavani)\
**Post date:** [November 13, 2026, 12:13pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/4 "2026-11-13T12:13:13Z")

</div>

Hi @Yanlin,  
Thanks for looking into this. Here are the details:

1. The operations that trigger the errors:

- User abc: POST /jaeger-\*/\_msearch → denied on indices:data/read/msearch
- User xyz: POST /\_search/scroll → denied on indices:data/read/scroll

2. We are querying via REST API through service clients. No OpenSearch Dashboards involved.

3. authinfo output when authenticated as each affected user:

For user abc:  
{  
“user\_name”: “abc”,  
“principal”: “CN=abc”,  
“peer\_certificates”: “1”,  
“backend\_roles”: [],  
“roles”: [“dst\_query”, “Dst-Query-role”],  
“tenants”: {“abc”: true}  
}  
For user xyz:  
{  
“user\_name”: “xyz”,  
“principal”: “CN=xyz”,  
“peer\_certificates”: “1”,  
“backend\_roles”: [],  
“roles”: [“OSS-DDC-role”],  
“tenants”: {“xyz”: true}  
}

Both users authenticate via client certificate (as shown by peer\_certificates: “1” and the CN-based principal). The role mappings resolve correctly — dst\_query /  
Dst-Query-role for abc and OSS-DDC-role for xyz — matching exactly the RolesChecked in the error logs.

The roles and role mappings were unchanged across the upgrade from 3.4.0 to 3.9.0. This same configuration worked without issues on 3.4.0. After upgrading to 3.9.0,  
indices:data/read/msearch and indices:data/read/scroll started requiring explicit permissions, even though they weren’t needed before.

Thanks

---

<div class="post-metadata">

**Author:** ![pavani](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@pavani](https://forum.opensearch.org/u/pavani)\
**Post date:** [November 13, 2026, 12:14pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/5 "2026-11-13T12:14:51Z")

</div>

Hi,

It says the page is temporarily unavailable.

Thanks

---

<div class="post-metadata">

**Author:** ![Yanlin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/yanlin/32/10286_2.png) [@Yanlin](https://forum.opensearch.org/u/Yanlin)\
**Post date:** [November 16, 2026, 9:53pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/6 "2026-11-16T21:53:30Z")

</div>

Hi @pavani,

I initially tested an in-place upgrade from OpenSearch 3.4.0 to 3.9.0, but I wasn’t able to reproduce the reported permission errors.I then performed some further testing on 3.9.0 with adjusted role permissions and was able to reproduce both errors. After explicitly adding the required permissions, both `_msearch` and `_search/scroll` requests succeeded in my lab.

Could you try adding the missing permissions to the relevant roles using the following API?

```http
PATCH /_plugins/_security/api/roles/{role_name}
[
  {
    "op": "add",
    "path": "/cluster_permissions/-",
    "value": "{permission_name}"
  }
]

```

Replace `{role_name}` with the relevant role and `{permission_name}` with either `indices:data/read/msearch` or `indices:data/read/scroll`, as appropriate.

Please check the existing role permissions before applying the changes, and let me know whether this helps resolve the issue.

Thanks!

---

<div class="post-metadata">

**Author:** ![pavani](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@pavani](https://forum.opensearch.org/u/pavani)\
**Post date:** [November 18, 2026, 4:03am UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/7 "2026-11-18T04:03:05Z")

</div>

Hi @Yanlin,

Thanks for the workaround. However, my question is - what changed in 3.9.0 that caused the authorization errors, which worked fine in 3.4.0. I couldn’t find anything related in the breaking changes either. Could you clarify what changed between these versions? Also, is there an alternative solution rather than explicitly adding these permissions to the roles every time?

Thanks

---

<div class="post-metadata">

**Author:** ![Yanlin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/yanlin/32/10286_2.png) [@Yanlin](https://forum.opensearch.org/u/Yanlin)\
**Post date:** [November 18, 2026, 6:04pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/8 "2026-11-18T18:04:59Z")

</div>

Hi @pavani,

I looked further into this and found that, starting with OpenSearch 3.8.0, the default mapping of `own_index` to all users (`*`) was removed from the default Security Configuration. The role itself still exists and includes the `cluster_composite_ops` permissions group, which provides permissions such as `indices:data/read/msearch`.

This change is documented here: [fix(config)!: remove own\_index default roles mapping by robertpaschedag · Pull Request #6147 · opensearch-project/security · GitHub](https://github.com/opensearch-project/security/pull/6147)

In a separate test on OpenSearch 3.4.0, removing the `*` mapping from `own_index` reproduced the reported `msearch` permission error. However, the PR discussion indicates that this change should affect newly configured clusters rather than automatically modify existing role mappings. In my in-place upgrade test from 3.4.0 to 3.9.0, the `own_index` mapping was preserved, and I couldn’t reproduce the reported errors.

I also noticed that `own_index` is not listed among the effective roles in your `authinfo` output.  
Could you clarify how the upgrade from 3.4.0 to 3.9.0 was performed, and whether any Security Configuration was exported, imported, or re-applied during the process?

Could you also share the current `own_index` role mapping?

```auto
GET /_plugins/_security/api/rolesmapping/own_index

```

Please redact any sensitive information before sharing.

Thanks!

---

<div class="post-metadata">

**Author:** ![cwperks](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/cwperks/32/4968_2.png) [@cwperks](https://forum.opensearch.org/u/cwperks)\
**Post date:** [November 19, 2026, 5:52pm UTC](https://forum.opensearch.org/t/no-permissions-for-indices-data-read-msearch-indices-data-read-scroll/28391/9 "2026-11-19T17:52:21Z")

</div>

Confirmed that its due to the `own_index` removal and an oversight of what that change would remove.

In the `own_index` static role config (defined: [security/src/main/resources/static\_config/static\_roles.yml at main · opensearch-project/security · GitHub](https://github.com/opensearch-project/security/blob/main/src/main/resources/static_config/static_roles.yml#L85-L96) ) it does grant `cluster_composite_ops` so make sure your roles mappings have this.
