[DOCS] Fixes links to role management APIs

This commit is contained in:
lcawl 2018-08-17 10:45:48 -07:00
parent f20b9b9efb
commit 34b140b2ba
3 changed files with 4 additions and 4 deletions

View file

@ -6,7 +6,7 @@ experimental[This API is *experimental* and may be changed or removed completely
The role management API allows people to manage roles that grant <<kibana-privileges>>.
It is *not* supported to do so using the
{ref}/security-api-roles.html[{es} Role Management APIs], and doing
{ref}/security-api.html#security-api-roles[{es} role management APIs], and doing
so will likely cause {kib}'s authorization to behave unexpectedly.
* <<role-management-api-put>>

View file

@ -70,7 +70,7 @@ The application is created by concatenating the prefix of `kibana-` with the val
}
----------------------------------
Roles that grant <<kibana-privileges>> should be managed using the <<role-management-api>> or the *Management* / *Security* / *Roles* page, not directly using the {es} {ref}/security-api-roles.html[Role Management API]. This role can then be assigned to users using {es}'s {ref}/security-api-users.html[User Management APIs].
Roles that grant <<kibana-privileges>> should be managed using the <<role-management-api>> or the *Management* / *Security* / *Roles* page, not directly using the {es} {ref}/security-api.html#security-api-roles[role management API]. This role can then be assigned to users using {es}'s {ref}/security-api-users.html[User Management APIs].
[[development-rbac-authorization]]
==== Authorization

View file

@ -29,8 +29,8 @@ see {xpack-ref}/authorization.html[Configuring Role-based Access Control].
[NOTE]
============================================================================
Managing roles that grant <<kibana-privileges>> using {es}'s {ref}
/security-api-roles.html[Role Management APIs] is not supported. Doing so will likely
Managing roles that grant <<kibana-privileges>> using the {es}
{ref}/security-api.html#security-api-roles[role management APIs] is not supported. Doing so will likely
cause Kibana's authorization to behave unexpectedly.
============================================================================