You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kaituo opened this issue
Sep 25, 2024
· 0 comments
· Fixed by #4774
Assignees
Labels
bugSomething isn't workinguntriagedRequire the attention of the repository maintainers and may need to be prioritizedv2.18.0Issues targeting release v2.18.0
What is the bug?
We added the .opensearch-forecast-state index to the system indices via this pull request by implementing the SystemIndexPlugin.getSystemIndexDescriptors method. I am unable to write to this system index using the admin user, but I can perform search queries. This behavior is inconsistent with other system indices added via an OpenSearch setting, where the admin user cannot write or search.
How can one reproduce the bug?
Steps to reproduce the behavior:
As the super admin, create the system indices .opensearch-forecast-state and .opendistro-anomaly-detectors, and add some content to them.
.opensearch-forecast-state is registered as a system index via SystemIndexPlugin.getSystemIndexDescriptors.
.opendistro-anomaly-detectors is registered as a system index via an OpenSearch setting.
The admin user cannot write to either index, which is the expected behavior.
(base) kaituo@88665a53bc93 github % curl -XPUT 'https://localhost:9200/.opensearch-forecast-state/_doc/1' -u admin:myStrongPassword123! --insecure -H 'Content-Type: application/json' -d'
{
"title": "Document with ID 1",
"content": "This document has a specific ID of 1.",
"date": "2023-10-06"
}
'
{"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null]"},"status":403}%
(base) kaituo@88665a53bc93 github % curl -XPUT 'https://localhost:9200/.opendistro-anomaly-detectors/_doc/1' -u admin:myStrongPassword123! --insecure -H 'Content-Type: application/json' -d'
{
"title": "Document with ID 1",
"content": "This document has a specific ID of 1.",
"date": "2023-10-06"
}
'
{"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null]"},"status":403}%
The admin user can query .opensearch-forecast-state but cannot query .opendistro-anomaly-detectors. This is inconsistent behavior.
What is the expected behavior?
The admin user should not be able to query the .opensearch-forecast-state system index, consistent with the behavior of other system indices added via OpenSearch settings.
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered:
kaituo
added
bug
Something isn't working
untriaged
Require the attention of the repository maintainers and may need to be prioritized
labels
Sep 25, 2024
bugSomething isn't workinguntriagedRequire the attention of the repository maintainers and may need to be prioritizedv2.18.0Issues targeting release v2.18.0
What is the bug?
We added the
.opensearch-forecast-state
index to the system indices via this pull request by implementing theSystemIndexPlugin.getSystemIndexDescriptors
method. I am unable to write to this system index using the admin user, but I can perform search queries. This behavior is inconsistent with other system indices added via an OpenSearch setting, where the admin user cannot write or search.How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The admin user should not be able to query the .opensearch-forecast-state system index, consistent with the behavior of other system indices added via OpenSearch settings.
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
opensearch-project/OpenSearch#14415
#4471
opensearch-project/anomaly-detection#1251
The text was updated successfully, but these errors were encountered: