Possible keys are:Ī complex data structure containing all authentication providers. Key-value pairs indicating which audit trail sections should be enabled. See the following resources for more information on working with the Splunk REST API.Audit trail settings and authentication providers are modified with the following parameters. The eai:attributes element shows the mandatory and optional fields. For more information, see Access Control List in the REST API User Manual. Note: You can append /_acl to an endpoint to access its ACL properties. Indicates if an admin or user with sufficient permissions can remove the entity. Properties that indicate write permissions of the resource. ![]() Properties that indicate read permissions of the resource. Set to false for items not controlled by ACLs, such as items under /server/logger. Indicates whether or not you can change the Access Control List (ACL). Indicates whether or not the current user can edit this item.Ī value of nobody indicates that all users have access to the resource, but that write access to the resource might be restricted. Indicates whether or not the current user can change the sharing state. Allowed values are:įor internal use only for the Splunk Web manager UI. ![]() The ACL includes the following parameters. The REST implementation enforces ownership and permissions for a resource based on application context namespace. These elements are also elided from the response examples to make the documentation easier to read. In handler 'datamodelgenerate': The following required arguments are missing: sid.ĮAI response data, the and elements, typically apply to all endpoints and are configuration-dependent, so redundant explanation is omitted. Requests with an error, such as a missing required parameter, can prompt an error response like the following example. Standard HTTP status codes are not included in endpoint documentation, but status codes with specific meaning for an endpoint and/or operation are noted. Returned values specific to the resource and/or operation are listed along with their descriptions. The response to GET and other requests typically includes key-value pairs representing details about the resource that you are accessing. True = Summarized response, omitting some index details, providing a faster response. Otherwise, collate alphabetically.Īlpha = Collate alphabetically, not case-sensitive.Īlpha_case = Collate alphabetically, case-sensitive. (Requires URI-encoding.)Īuto = If all field values are numeric, collate numerically. Search=field_name%3Dfield_value restricts the match to a single field. Search=foo matches on any field with the string foo in the name. Response filter, where the response field values are matched against this search expression. Specify multiple times to return multiple values.į=qualifiedSearch returns only the value for qualifiedSearch.į=s* returns all the values that have names beginning with s.į=qualifiedSearch&f=is_visible returns the values for qualifiedSearch as well as is_visible. Set value to 0 to get all available entries.įilters the response to include only the named values. In addition to the parameters specific to each endpoint and operation, the following request parameters are valid for some GET methods. Request and response details Pagination and filtering parameters
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |