anchor.diff:      </filter-class>
       <init-param>
         <param-name>org.uberfire.cookie.id</param-name>
  -      <param-value>errai-cdi-workbench-cookie</param-value>
  +      <param-value>uberfire-tutorial-cookie</param-value>
  +    </init-param>
  +    <init-param>
  +      <param-name>org.uberfire.auth.force.url</param-name>
  +      <param-value>/UberFireTutorial/UberFire.html</param-value>
       </init-param>
     </filter>
   
  
positive.code: The `UberFireSecurityFilter` is mapped to `/*` and so it is consulted
  for every request to a servlet or static resource in your web
  application. In other words, this filter makes an allow/deny decision
  for every HTTP request to your application.
  
  How do you control the behaviour of this filter? It depends.  The
  filter relies on a series of pluggable mechanisms to make its
  decisions about how users can identify themselves, which
  username+password combinations are valid, and which URLs anonymous and
  authenticated users are allowed to access.
  
  For this demo, we will control access using the default settings, which are:
  
  * Authentication Manager (controls login and logout): `HttpAuthenticationManager`
  ** Authentication Schemes (extract provided credentials from HTTP requests):
  
negative.code:    - /*.ico
     - /UberFireTutorial/images/**
     - /UberFireTutorial/css/**
     - /login.jsp
  ---------
  
  This example file shows you how to restrict certain URL paths to
  certain roles, and also how to exclude some paths from the
  authentication and authorization checks altogether.
  
  === Enable the UberFire security CDI interceptors
  
  