libre.sh/keycloak-scim
4
0
Fork 0
Code Issues 15 Pull requests Releases 1 Activity Actions

Merge pull request #30 from jenmalloy/RHSSO-844

Browse source 
fixed RHSSO-844: header issue in Server Admin Guide
This commit is contained in:
Jen Malloy 2017-03-09 12:19:04 -05:00 committed by GitHub
commit 3d57b71e5e
2 changed files with 11 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
server_admin/topics/roles/client-roles.adoc
View file

@ -1,11 +1,10 @@
=== Client Roles === Client Roles
Client roles are basically a namespace dedicated to a client. Each client gets its own namespace. Client roles are managed 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.
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` `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.

14
server_admin/topics/roles/realm-roles.adoc
View file

@ -1,22 +1,18 @@
=== Realm Roles === Realm Roles
Realm level roles are a global namespace to define your roles. You can see the list of built-in and created 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 the `Roles` left menu item.
by clicking on the `Roles` left menu item.
image:../../{{book.images}}/roles.png[] 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 To create a role, click *Add Role* on this page, enter in the name and description of the role, and click *Save*.
and hit the `Save` button.
.Add Role .Add Role
image:../../{{book.images}}/role.png[] image:../../{{book.images}}/role.png[]
The value for the `description` field is localizable by specifying a substitution variable with `$\{var-name}` strings. 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.
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.
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` `scope=admin user`