Task #1713
User collections are inaccessible
100%
Associated revisions
Added link to edit ACLs for the lookup
Reference #1713
History
#1 Updated by Luke Murphey almost 8 years ago
- Subject changed from User collections are not accessible to User collections are inaccessible
Some questions:
- Is this fixed by making the collection as a non-admin user?
- Can this be fixed with a local.meta change
#2 Updated by Luke Murphey almost 8 years ago
- Target version set to 2.6
#3 Updated by Luke Murphey almost 8 years ago
Steps to repro:
- Make a collection with the admin user
- Try to load the collection as a non-admin
#4 Updated by Luke Murphey almost 8 years ago
- Status changed from New to In Progress
#5 Updated by Luke Murphey almost 8 years ago
These appear to be getting made in the admin user. Perhaps I should make them in the nobody user?
#6 Updated by Luke Murphey almost 8 years ago
The lookups are still made with the admin user even when the owner is set to "nobody".
#7 Updated by Luke Murphey almost 8 years ago
I wonder, can a user load the lookup under their own account?
#8 Updated by Luke Murphey almost 8 years ago
You can load a lookup under your user account but it is defined as read-only.
#9 Updated by Luke Murphey almost 8 years ago
The API doesn't seem to indicate any way to make the lookup readable by other people.
See http://docs.splunk.com/Documentation/Splunk/6.3.0/RESTREF/RESTkvstore
#10 Updated by Luke Murphey almost 8 years ago
- https://answers.splunk.com/answers/144000/modifying-acl-saved-search-permissions-through-rest-api-using-python.html
- https://answers.splunk.com/answers/388854/how-can-i-change-the-permissions-of-dynamically-cr.html
- https://answers.splunk.com/answers/48646/modify-event-types-via-api-curl.html
- https://answers.splunk.com/answers/115781/change-the-owner-of-a-saved-search-via-rest.html
#11 Updated by Luke Murphey almost 8 years ago
I have this wired up but I am getting the following error against /servicesNS/nobody/lookup_editor/storage/collections/config/test_lookup_nobody/_acl:
action=_acl is not supported on individual entities
You can see this by navigating to https://127.0.0.1:8089/servicesNS/nobody/lookup_editor/storage/collections/config/test_lookup_nobody/_acl
#12 Updated by Luke Murphey almost 8 years ago
Same error on a CSV lookup: https://127.0.0.1:8089/servicesNS/nobody/lookup_editor/data/lookup-table-files/test_lookup_nobody.csv/_acl and https://127.0.0.1:8089/services/data/lookup-table-files/test_lookup_nobody.csv/_acl
Maybe I am doing this wrong.
#13 Updated by Luke Murphey almost 8 years ago
This can be adjusted within Core: http://dev.splunk.com/view/webframework-developapps/SP-CAAAE88
For example, see:
#14 Updated by Luke Murphey almost 8 years ago
You can edit the ACLs for these files in the Manager. To this end, I have added a link to open the editor from the lookup editor.
#15 Updated by Luke Murphey almost 8 years ago
- % Done changed from 0 to 90
#16 Updated by Luke Murphey over 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100