LDAP groups error with different index

Security
3

Hi @aetter , I had the same exaact issue …

Getting 403 security exception on :
/api/saved_objects/_find?type=index-pattern&fields=title&search=*&search_fields=title&per_page=1

error: "Forbidden"
message: "no permissions for [indices:data/read/search] and User [name=ldap_ads_user, roles=[PRC-USER-GROUP], requestedTenant=null]: [security_exception] no permissions for [indices:data/read/search] and User [name=ldap_ads_user, roles=[PRC-USER-GROUP], requestedTenant=null]"
statusCode: 403

Role for PRC-USER-GROUP:

{
  "cluster": [],
  "indices": {
    "index1-*": {
      "*": [
        "READ"
      ]
    }
  },
  "tenants": {}
}

Role Mapping :

 { 
      "backendroles": [
      "PRC-USER-GROUP"
      ],
     "hosts": [],
      "users": []
    }

LDAP login is working fine with the auth info api call populating backend roles array with the above PRC group.

is there any other additional step missing in mapping the role to appropriate indices ?
EDIT 1:

If i replace the mapping with it works fine.

{
      "cluster": [],
      "indices": {
        "*": {
          "*": [
            "READ"
          ]
        }
      },
      "tenants": {}
    }

Even the specific Index name also , experiencing the same failure:

{
      "cluster": [],
      "indices": {
        "index1-2342": {
          "*": [
            "READ"
          ]
        }
      },
      "tenants": {}
    }

After trial runs , Found the solution :

{
  "cluster": [],
  "indices": {
    "index1-*": {
      "*": ["READ"]
    },
    "?kibana*": {
      "*": ["READ"]
    }
  },
  "tenants": {}
}

Add the second pattern as well and it gave access to the pattern of the indices that is needed to build in management. Having kibanauser in the backend role didnt fix the issue for my case.