anchor.diff:  ----
   * Constraint the remote services URL patterns as:
   +
  -[source]
  +[source,xml]
   ----
   <security-constraint>
     <web-resource-collection>
  
positive.code: The result of the integration with Keycloak has lots of advantages such as:
  
  * Provide an integrated SSO and IDM environment for different clients, including jBPM and Drools workbenches
  * Social logins - use your Facebook, Google, Linkedin, etc accounts
  * User session management
  * And much more...
  
  
negative.code: </security-constraint>
  ----
  
  [IMPORTANT]
  ====
  The user that consumes the remote services must be member of role __rest-all__.
  As on described previous steps, the _admin_ user in this example it's already a member of the __rest-all __role.
  ====
  
  == Securing workbench's file system services via Keycloak
  
  
  In order to consume other remote services such as the file system ones (e.g. remote GIT),
  a specific **Keycloak login module must be used** for the application's security domain in the
  __$JBPM_HOME/standalone/configuration/standalone-full.xml__ file.
  By default the workbench uses the __other__ security domain, so the resulting  configuration on the
  __$JBPM_HOME/standalone/configuration/standalone-full.xml__ should be such as:
  
  [source,xml]
  ----
  <security-domain name="other" cache-type="default">
      <authentication>
  