Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Read only users see "[security_exception] no permissions" when looking at index patterns that point to no indices #5169

Open
jhenley-icr-team opened this issue Feb 15, 2025 · 2 comments
Labels
bug Something isn't working triaged Issues labeled as 'Triaged' have been reviewed and are deemed actionable.

Comments

@jhenley-icr-team
Copy link

Describe the bug

Currently we have many read only users who will occasionally run into a bug where if they open an index pattern that points to no indices they see the below error

Error fetching fields for index pattern cognos1291_test_datasource_scripted_pattern (ID: cognos1291_test_datasource_scripted_pattern)

[object Object]: [security_exception] no permissions for [indices:data/read/field_caps] and User [name=/cn=cognos base user, ou=integration, o=cognos, l=aurora, st=colorado]

This causes confusion for users as it gives them the impression they cannot see the info, not that there is no data.

Related component

No response

To Reproduce

  1. Create an index pattern that points to no indices (easiest way to force it is to create an index pattern pointing at an index which is then deleted)
  2. As a user with read only permissions
  3. Go to Dashboards Management, select the created index pattern above
  4. See error like below image

Image

Expected behavior

Would expect that for a read only user that they would also see the same much more descriptive error that a user with read and write can see

Image

Additional Details

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@jhenley-icr-team jhenley-icr-team added bug Something isn't working untriaged Require the attention of the repository maintainers and may need to be prioritized labels Feb 15, 2025
@andrross
Copy link
Member

This looks like logic related to authorization, so it probably belongs in the security repository.

@opensearch-project/admin Can you transfer this to the security repo?

@gaiksaya gaiksaya transferred this issue from opensearch-project/OpenSearch Mar 10, 2025
@cwperks cwperks added triaged Issues labeled as 'Triaged' have been reviewed and are deemed actionable. and removed untriaged Require the attention of the repository maintainers and may need to be prioritized labels Mar 17, 2025
@cwperks
Copy link
Member

cwperks commented Mar 17, 2025

[Triage] Thank you for filing this issue @jhenley-icr-team w/ reproduction steps. Marking this issue as triaged, I am not familiar with the field capabilities call that dashboards is making here and how the index resolution works for that call. I will take a deeper look at this to understand what indices are being resolved to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triaged Issues labeled as 'Triaged' have been reviewed and are deemed actionable.
Projects
None yet
Development

No branches or pull requests

3 participants