IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Get role mappings API
editGet role mappings API
editRetrieves role mappings.
Prerequisites
edit-
To use this API, you must have at least the
read_securitycluster privilege.
Description
editRole mappings define which roles are assigned to each user. For more information, see Mapping users and groups to roles.
The role mapping APIs are generally the preferred way to manage role mappings rather than using role mapping files. The get role mappings API cannot retrieve role mappings that are defined in role mapping files.
Path parameters
edit-
name - (Optional, string) The distinct name that identifies the role mapping. The name is used solely as an identifier to facilitate interaction via the API; it does not affect the behavior of the mapping in any way. You can specify multiple mapping names as a comma-separated list. If you do not specify this parameter, the API returns information about all role mappings.
Response body
editA successful call retrieves an object, where the keys are the names of the request mappings, and the values are the JSON representation of those mappings. For more information, see Role mapping resources.
Response codes
editIf there is no mapping with the requested name, the
response will have status code 404.
Examples
editThe following example retrieves information about the mapping1 role mapping:
resp = client.security.get_role_mapping(
name="mapping1",
)
print(resp)
const response = await client.security.getRoleMapping({
name: "mapping1",
});
console.log(response);
GET /_security/role_mapping/mapping1
{
"mapping1": {
"enabled": true,
"roles": [
"user"
],
"rules": {
"field": {
"username": "*"
}
},
"metadata": {}
}
}