anchor.diff:  but because it matches the `deny1` permission set's path on a longer match, `deny1` will be chosen and the request will
   be rejected.
   
  -### Matching multiple paths: most specific method wins
  +=== Matching multiple paths: most specific method wins
   
   If a path is registered with multiple permission sets then any permission sets that specify a HTTP method will take
   precedence and permissions sets without a method will not be considered (assuming of course the method matches). In this
  
positive.code: ...
  ----
  
  ## Security Identity Customization
  
  Internally, the identity providers create and update an istance of the `io.quarkus.security.identity.SecurityIdentity` class which holds the principal, roles, credentials which were used to authenticate the client (user) and other security attributes. An easy option to customize `SecurityIdentity` is to register a custom `SecurityIdentityAugmentor`, for example, the augmentor below adds an addition role:
  
  
negative.code: It is also possible to define role based policies, as shown in the example. These policies will only allow users with the
  specified roles to access the resources.
  
  === Matching on paths, methods
  
  Permission sets can also specify paths and methods as a comma separated list. If a path ends with '*' then it is considered
  to be a wildcard match and will match all sub paths, otherwise it is an exact match and will only match that specific path:
  