anchor.diff:  === OSGi HTTP Service
   
   The _canonical_ way of using servlets in OSGi environment is to use `org.osgi.service.http.HttpService` specified
  -in "102 Http Service Specification" in OSGi Enteprise R6 document.
  +in "102 Http Service Specification" in OSGi Enterprise R6 document.
   However it allows to register only `javax.servlet.Servlet` instances and _resources_ (which are effectively
   resource-service servlets).
   
  
positive.code: 
  `org.keycloak.adapters.osgi.undertow.CxfKeycloakAuthHandler` is one of such handlers that's integrating CXF
  engine with Keycloak. Using `org.keycloak.adapters.osgi.PathBasedKeycloakConfigResolver` as Keycloak configuration
  resolver allows us to configure an endpoing using well known `etc/<context>-keycloak.json`.
  
  because we have two endpoints registered in separate CXF server engine, we need two files:
  
  
negative.code: The below sections refer to single Keycloak _realm_ created in Keycloak server ${version.org.keycloak} for the purpose
  of Fuse 7 Security/Keycloak quickstarts.
  
  The keycloak server is running using standard distribution with shifted ports:
  [listing,options="nowrap"]
  ----
  $ bin/standalone.sh -Djboss.socket.binding.port-offset=100 --debug 5006
  