anchor.diff:  
   Last step for being able to use the _demo_ realm from the jBPM workbench is create the application's user and roles:
   
  -* Go to the Roles section and create the roles _admin_, _kiemgmt_ and _rest-all_
  -* Go to the Users section and create the _admin_ user. Set the password with value "password" in the credentials tab, unset the temporary switch.
  -* In  the Users section navigate to the _Role Mappings_ tab and assign the _admin_, _kiemgmt_ and _rest-all_ roles to the _admin_ user
  +* Go to the Roles section and create the roles __admin__, __kiemgmt__ and __rest-all__
  +* Go to the Users section and create the __admin__ user. Set the password with value __password__ in the credentials tab, unset the temporary switch.
  +* In  the Users section navigate to the _Role Mappings_ tab and assign the __admin__, __kiemgmt__ and __rest-all__ roles to the __admin__ user
   +
   
   
  
positive.code: ----
  curl -H "Authorization: bearer $TOKEN" http://localhost:8080/kie-wb-x.y.z.Final/rest/repositories
  ----
  
negative.code: * *Consuming remote services*
  + 
  This section describes how a third party clients can consume the remote service endpoints provided by both Workbench and Execution Server, such as the REST API or remote file system services.
  * *Keycloakd and the Workbench's security administration area*
  
  
  == Scenario
  