anchor.diff:  
   == Test the changes
   
  -- Access allowed
  +Access allowed::
   
   Open your browser again to http://localhost:8080/greeting and introduce `scott` and `jb0ss` in the dialog displayed.
  -
  ++
   The word `hello` should be displayed.
   
  -- Access forbidden
  +Access forbidden::
   
   Open your browser again to http://localhost:8080/greeting and let empty the dialog displayed.
  -
  ++
   The result should be:
  ++
  +[source]
   ----
   Access to localhost was denied
   You don't have authorization to view this page.
  
positive.code:     }
  }
  ----
  
  <1> `doSomething` can be executed if the current logged in user is the same as the `username` method parameter
  <2> `doSomethingElse` can be executed if the current logged in user is the same as the `name` field of `person` method parameter
  
  *Tip* the use of `authentication.` is optional, so using `principal.username` has the same result.
  
  #paramName != authentication.principal.username:: This is similar to the previous expression with the difference being that the method parameter must different than the logged in username.
  
  @beanName.method():: This syntax allows developers to specify that the execution of method of a specific bean will determine if the current user can access the secured method.
  +The syntax is best explained with an example.
  +Let's assume that a `MyComponent` bean has been created like so:
  
  [source,java]
  ----
  @Component
  
negative.code: Quarkus provides support for some of the most used features of Spring Security's `@PreAuthorize` annotation.
  The expressions that are supported are the following:
  
  hasRole::
  +
  To test if the current user has a specific role, the `hasRole` expression can be used inside `@PreAuthorize`.
  +
  Some examples are: `@PreAuthorize("hasRole('admin')")`, `@PreAuthorize("hasRole(@roles.USER)")` where the `roles` is a bean that could be defined like so:
  +
  [source, java]
  ----
  import org.springframework.stereotype.Component;
  