-
Notifications
You must be signed in to change notification settings - Fork 274
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] Roles inconsistency #4730
Comments
I have found the static roles in the source code: https://github.com/opensearch-project/security/blob/2.16.0.0/src/main/resources/static_config/static_roles.yml There is for example: security/src/main/resources/static_config/static_roles.yml Lines 24 to 51 in 3076016
In Lines 5 to 8 in 3076016
Why these two have "so" different content? |
[Triage] @n9
A user mapped to this role can view saved objects, but cannot save saved objects. Saved objects is a generic term for items such as:
Closing this issue. Please let me know if you need any further information. For general questions I would also recommend posting on the OpenSearch forum: https://forum.opensearch.org/c/security/3 |
@cwperks What about the bug that the default roles file is not empty? (But according to the documentation it should be.) |
@n9 You're right, that should be changed. The |
@n9 Opened a documentation PR here: opensearch-project/documentation-website#8334 |
@cwperks But why |
I can't really tell based on the history: #96 There is some overlap between the meanings of "reserved" and "static" and if I had to guess, it was added to This comment goes into the difference between static and reserved: #4387 (comment) |
What is the bug?
The current documentation says:
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
Either the file should be empty or the documentation should not say that.
What is your host/environment?
Do you have any screenshots?
Not needed.
Do you have any additional context?
Is this still true? Where I can find it in the source code?
The text was updated successfully, but these errors were encountered: