File tree Expand file tree Collapse file tree 2 files changed +7
-2
lines changed
en/security/authorization Expand file tree Collapse file tree 2 files changed +7
-2
lines changed Original file line number Diff line number Diff line change @@ -81,7 +81,6 @@ buildRestTests.expectedUnconvertedCandidates = [
81
81
' en/rest-api/ml/validate-job.asciidoc' ,
82
82
' en/rest-api/security/authenticate.asciidoc' ,
83
83
' en/rest-api/watcher/stats.asciidoc' ,
84
- ' en/security/authorization/managing-roles.asciidoc' ,
85
84
' en/watcher/example-watches/watching-time-series-data.asciidoc' ,
86
85
]
87
86
Original file line number Diff line number Diff line change @@ -12,6 +12,8 @@ A role is defined by the following JSON structure:
12
12
"indices": [ ... ] <3>
13
13
}
14
14
-----
15
+ // NOTCONSOLE
16
+
15
17
<1> A list of usernames the owners of this role can <<run-as-privilege, impersonate>>.
16
18
<2> A list of cluster privileges. These privileges define the
17
19
cluster level actions users with this role are able to execute. This field
@@ -37,6 +39,8 @@ The following describes the structure of an indices permissions entry:
37
39
"query": "..." <4>
38
40
}
39
41
-------
42
+ // NOTCONSOLE
43
+
40
44
<1> A list of indices (or index name patterns) to which the permissions in this
41
45
entry apply.
42
46
<2> The index level privileges the owners of the role have on the associated
@@ -77,8 +81,9 @@ The following snippet shows an example definition of a `clicks_admin` role:
77
81
78
82
[source,js]
79
83
-----------
84
+ POST /_xpack/security/role/clicks_admin
80
85
{
81
- "run_as": [ "clicks_watcher_1" ]
86
+ "run_as": [ "clicks_watcher_1" ],
82
87
"cluster": [ "monitor" ],
83
88
"indices": [
84
89
{
@@ -92,6 +97,7 @@ The following snippet shows an example definition of a `clicks_admin` role:
92
97
]
93
98
}
94
99
-----------
100
+ // CONSOLE
95
101
96
102
Based on the above definition, users owning the `clicks_admin` role can:
97
103
You can’t perform that action at this time.
0 commit comments