From 840471159da5b270722d31d3095495cd30d10f33 Mon Sep 17 00:00:00 2001 From: Jen Malloy Date: Thu, 9 Mar 2017 12:17:51 -0500 Subject: [PATCH] fixed RHSSO-844: header issue in Server Admin Guide --- server_admin/topics/roles/client-roles.adoc | 13 ++++++------- server_admin/topics/roles/realm-roles.adoc | 14 +++++--------- 2 files changed, 11 insertions(+), 16 deletions(-) diff --git a/server_admin/topics/roles/client-roles.adoc b/server_admin/topics/roles/client-roles.adoc index cafad3ba57..ffa262559e 100644 --- a/server_admin/topics/roles/client-roles.adoc +++ b/server_admin/topics/roles/client-roles.adoc @@ -1,11 +1,10 @@ === Client Roles -Client roles are basically a namespace dedicated to a client. Each client gets its own namespace. Client roles are managed -under the `Roles` tab under each individual client. You interact with this UI the same way you do for realm level roles. +Client roles are basically a namespace dedicated to a client. Each client gets its own namespace. Client roles are managed under the `Roles` tab under each individual client. You interact with this UI the same way you do for realm-level roles. + +If the client has to explicitly request another client's role, the role has to prefixed with the client ID when performing a request using the scope parameter. For example, if the client ID is `account` and the role is `admin`, the scope parameter is: -If the client has to explicitly request for another client's role, the role has to prefixed with the client's id when requesting via the scope parameter. For example, if the client id is `account` and the role is `admin`, the scope parameter should be: - `scope=account/admin` - - As noted in the realm roles section, multiple roles are separated by spaces. - + +As noted in the realm roles section, multiple roles are separated by spaces. + diff --git a/server_admin/topics/roles/realm-roles.adoc b/server_admin/topics/roles/realm-roles.adoc index 19dfab6802..118f8b3d8d 100644 --- a/server_admin/topics/roles/realm-roles.adoc +++ b/server_admin/topics/roles/realm-roles.adoc @@ -1,22 +1,18 @@ === Realm Roles -Realm level roles are a global namespace to define your roles. You can see the list of built-in and created roles -by clicking on the `Roles` left menu item. +Realm-level roles are a global namespace to define your roles. You can see the list of built-in and created roles by clicking the `Roles` left menu item. image:../../{{book.images}}/roles.png[] -To create a role just click on the `Add Role` button on this page, enter in the name and description of the role -and hit the `Save` button. +To create a role, click *Add Role* on this page, enter in the name and description of the role, and click *Save*. .Add Role image:../../{{book.images}}/role.png[] -The value for the `description` field is localizable by specifying a substitution variable with `$\{var-name}` strings. -The localized value is then configured within property files in your theme. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] -for more information on localization. If a client requires user _consent_, this description string will be displayed on the -consent page for the user. +The value for the `description` field is localizable by specifying a substitution variable with `$\{var-name}` strings. The localized value is then configured within property files in your theme. See the link:{{book.developerguide.link}}[{{book.developerguide.name}}] for more information on localization. If a client requires user _consent_, this description string is displayed on the consent page for the user. -If the client has to explicitly request for a realm role, set `Scope Param Required` to true. The role then has to be specified via the `scope` parameter when requesting a token. Multiple realm roles are separated by space: +If the client has to explicitly request for a realm role, set `Scope Param Required` to true. The role then has to be specified using the `scope` parameter when requesting a token. Multiple realm roles are separated by space: `scope=admin user` +