2016-08-31 17:53:47 +00:00
|
|
|
[[_manage_config]]
|
|
|
|
|
|
|
|
|
|
== Manage Subsystem Configuration
|
|
|
|
|
|
2017-08-28 12:50:14 +00:00
|
|
|
Low-level configuration of {project_name} is done by editing the
|
2016-08-31 17:53:47 +00:00
|
|
|
`standalone.xml`, `standalone-ha.xml`, or `domain.xml` file
|
|
|
|
|
in your distribution. The location of this file
|
2017-08-28 12:50:14 +00:00
|
|
|
depends on your <<_operating-mode, operating mode>>.
|
2016-08-31 17:53:47 +00:00
|
|
|
|
|
|
|
|
While there are endless settings you can configure here, this section will focus on
|
|
|
|
|
configuration of the _keycloak-server_ subsystem. No matter which configuration file
|
|
|
|
|
you are using, configuration of the _keycloak-server_ subsystem is the same.
|
|
|
|
|
|
|
|
|
|
The keycloak-server subsystem is typically declared toward the end of the file like this:
|
|
|
|
|
[source,xml]
|
|
|
|
|
----
|
|
|
|
|
<subsystem xmlns="urn:jboss:domain:keycloak-server:1.1">
|
|
|
|
|
<web-context>auth</web-context>
|
|
|
|
|
...
|
|
|
|
|
</subsystem>
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
Note that anything changed in this subsystem will not take effect until the server is rebooted.
|
