anchor.diff:  * The login modules on the __other__ security domain in the __$JBPM_HOME/standalone/configuration/standalone-full.xml__ file must be REPLACED by the above given one.
   * Replace __$JBPM_HOME/kie-git.json__ by the path (on file system) or the classpath (e.g. __classpath:/some-path/kie-git.json__) for the json configuration file used for the remote services client. Please continue reading in order to create this Keycloak client and how to obtain this json file.
   
  -At this point, remote services that use JAAS for the authentication process, such as the file system ones ( e.g. GIT ), are secured by Keycloak using the client specified in the above json configuration file. So let's create this client on Keycloak and generate the required JSON file:
  +At this point, remote services that use JAAS for the authentication process, such as the file system ones (e.g. GIT), are secured by Keycloak using the client specified in the above json configuration file. So let's create this client on Keycloak and generate the required JSON file:
   
   * Navigate to the http://localhost:8180/auth/admin[KC administration console] and create a new client for the __demo__ realm using __kie-git__ as name.
   * Enable __Direct Access Grants Enabled__ option
  
positive.code: You have two options to consume the different remove service endpoints:
  
  * Using basic authentication, if the application's client supports it
  * Using Bearer ( token) based authentication
  
  
  === Using basic authentication
  
negative.code: </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:
  
  * _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
  * _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 (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
  
  