anchor.diff:  
   Note: This example considers that the execution server will be configured to run using a port offset of 200, so the HTTP port will be available at localhost:8280.
   
  -=== Install and setup the KC adapter on the execution server
  +=== Install and set up the KC adapter on the execution server
   
   
   At this point, a client named _kie-execution-server_ is ready on the KC server to use from the execution server. 
   
  -Let's install, setup and deploy the execution server:
  +Let's install, set up and deploy the execution server:
   
   * Install another Wildfly server to use for the execution server and the KC client adapter as well. You can follow above instructions for the Workbench or follow the http://www.keycloak.org/docs/latest/securing_apps/index.html[securing applications guide]
   * Edit the _standalone-full.xml_ file from the Wildfly server's configuration path and configure the KC subsystem adapter as:
  
positive.code: 
  The Keycloak administration console will be available at http://localhost:8180/auth/admin/.
  
  == Create and setup the demo realm
  
  
  Security realms are used to restrict the access for the different application's resources.
  
negative.code: 
  image::Workbench/KeycloakSSOIntegration/admin_user_roles.png[align="center"]
  
  At this point a Keycloak server is running on the host, set up with a minimal configuration set.
  Let's move to the jBPM workbench set up.
  
  == Install and set up jBPM Workbench
  
  
  For this tutorial let's use a Wildfly as the application server for the jBPM workbench, as the jBPM installer does by default.
  