anchor.diff:  </subsystem>
   ----
   
  -If you have imported the example json files from this document in __step 2__, you can just use same configuration as above by using your concrete deployment name . Otherwise please use your values for these configurations:
  +If you have imported the example json files from this document in __step 2__, you can just use same configuration as above by using your concrete deployment name. Otherwise please use your values for these configurations:
   
   * _Name for the secure deployment_ - Use your concrete application's WAR file name
  -* _Realm_ - Is the realm that the applications will use, in our example, the __demo __realm created the previous step.
  -* _Realm Public Key_ - Provide here the public key for the __demo __realm. It's not mandatory, if it's not specified, it will be retrieved from the server. Otherwise, you can find it in the Keycloak admin console -> Realm settings ( for _demo_ realm ) -> Keys
  +* _Realm_ - Is the realm that the applications will use, in our example, the _demo_ realm created the previous step.
  +* _Realm Public Key_ - Provide here the public key for the _demo_ realm. It's not mandatory, if it's not specified, it will be retrieved from the server. Otherwise, you can find it in the Keycloak admin console -> Realm settings (for _demo_ realm) -> Keys
   * _Authentication server URL_ - The URL for the Keycloak's authentication server
   * _Resource_ - The name for the client created on step 2. In our example, use the value __kie__.
  -* __Enable basic auth __- For this example let's enable Basic authentication mechanism as well, so clients can use both Token (Baerer) and Basic approaches to perform the requests.
  -* _Credential_ - Use the password value for the __kie __client. You can find it in the Keycloak admin console -> Clients -> kie -> Credentials tab -> Copy the value for the __secret__.
  -
  -For this example you have to take care about using your concrete values for __secure-deployment name__, __realm-public-key
  -        __and __credential __password.
  -You can find detailed information about the KC adapter configurations https://keycloak.github.io/docs/userguide/keycloak-server/html/ch08.html#adapter-config[here].
  +* _Enable basic auth_ - For this example let's enable Basic authentication mechanism as well, so clients can use both Token (Bearer) and Basic approaches to perform the requests.
  +* _Credential_ - Use the password value for the _kie_ client. You can find it in the Keycloak admin console -> Clients -> kie -> Credentials tab -> Copy the value for the __secret__.
  +
  +For this example you have to take care about using your concrete values for _secure-deployment_ name, _realm-public-key_ and _credential_ password.
  +You can find detailed information about the https://keycloak.gitbooks.io/documentation/securing_apps/topics/oidc/java/jboss-adapter.html[JBoss EAP adapter configuration] in Keycloak documentation.
   
   === Run the environment
   
  
positive.code: ----
  * Constraint the remote services URL patterns as:
  +
  [source]
  ----
  <security-constraint>
    <web-resource-collection>
  
negative.code: Here are the steps for a minimal Keycloak installation and setup:
  
  * Download latest version of Keycloak from the http://keycloak.jboss.org/downloads[Downloads] section. This example is based on Keycloak 1.9.0.Final
  * Unzip the downloaded distribution of Keycloak into a folder, let's refer it as
  +
  [source]
  ----
  