parent
e6e724d585
commit
1332e53a97
5 changed files with 17 additions and 3 deletions
|
@ -77,4 +77,7 @@ include::topics/saml/mod-auth-mellon.adoc[]
|
|||
include::topics/docker/docker-overview.adoc[]
|
||||
include::topics/client-registration.adoc[]
|
||||
include::topics/client-registration/client-registration-cli.adoc[]
|
||||
ifeval::[{project_community}==true]
|
||||
include::topics/token-exchange/token-exchange.adoc[]
|
||||
endif::[]
|
||||
|
||||
|
|
|
@ -55,7 +55,9 @@ include::topics/sso-protocols.adoc[]
|
|||
include::topics/admin-console-permissions.adoc[]
|
||||
include::topics/admin-console-permissions/master-realm.adoc[]
|
||||
include::topics/admin-console-permissions/per-realm.adoc[]
|
||||
ifeval::[{project_community}==true]
|
||||
include::topics/admin-console-permissions/fine-grain.adoc[]
|
||||
endif::[]
|
||||
include::topics/assembly-managing-clients.adoc[]
|
||||
include::topics/vault.adoc[]
|
||||
include::topics/events.adoc[]
|
||||
|
|
|
@ -3,5 +3,9 @@
|
|||
== Controlling access to the Admin Console
|
||||
|
||||
Each realm created on the {project_name} has a dedicated Admin Console from which that realm can be managed.
|
||||
The `master` realm is a special realm that allows admins to manage more than one realm on the system. You can also
|
||||
define fine-grained access to users in different realms to manage the server. This chapter goes over all the scenarios for this.
|
||||
The `master` realm is a special realm that allows admins to manage more than one realm on the system.
|
||||
ifeval::[{project_community}==true]
|
||||
You can also
|
||||
define fine-grained access to users in different realms to manage the server.
|
||||
endif::[]
|
||||
This chapter goes over all the scenarios for this.
|
||||
|
|
|
@ -2,7 +2,10 @@
|
|||
= Advanced configuration
|
||||
[role="_abstract"]
|
||||
|
||||
After completing the fields on the *Settings* tab, you can use the other tabs to perform advanced configuration. For example, you can use the *Permissions* and *Roles* tabs to configure fine-grained authentication for administrators. See <<_fine_grain_permissions, Fine grain admin permissions>>. Also, see the remaining sections in this chapter for other capabilities.
|
||||
After completing the fields on the *Settings* tab, you can use the other tabs to perform advanced configuration.
|
||||
ifeval::[{project_community}==true]
|
||||
For example, you can use the *Permissions* and *Roles* tabs to configure fine-grained authentication for administrators. See <<_fine_grain_permissions, Fine grain admin permissions>>. Also, see the remaining sections in this chapter for other capabilities.
|
||||
endif::[]
|
||||
|
||||
== Advanced tab
|
||||
|
||||
|
|
|
@ -31,9 +31,11 @@ The following example shows how to limit the number of active `AuthenticationSes
|
|||
bin/kc.[sh|bat] start --spi-authentication-sessions-infinispan-auth-sessions-limit=100
|
||||
----
|
||||
|
||||
ifeval::[{project_community}==true]
|
||||
The equivalent command for the new map storage:
|
||||
|
||||
[source,bash]
|
||||
----
|
||||
bin/kc.[sh|bat] start --spi-authentication-sessions-map-auth-sessions-limit=100
|
||||
----
|
||||
endif::[]
|
||||
|
|
Loading…
Reference in a new issue