anchor.diff:  '''
   
   [[servlet-check-for-annotationconfigurationexceptions]]
  -[%interactive]
  -* [ ] Check for ``AnnotationConfigurationException``s
  +==== Check for ``AnnotationConfigurationException``s
   
   `@EnableMethodSecurity` and `<method-security>` activate stricter enforcement of Spring Security's non-repeatable or otherwise incompatible annotations.
   If after moving to either you see ``AnnotationConfigurationException``s in your logs, follow the instructions in the exception message to clean up your application's method security annotation usage.
  
positive.code: '''
  
  [[servlet-replace-permissionevaluator-bean-with-methodsecurityexpression-handler]]
  [%interactive]
  * [ ] Publish a `MethodSecurityExpressionHandler` instead of a `PermissionEvaluator`
  
  `@EnableMethodSecurity` does not pick up a `PermissionEvaluator`.
  This helps keep its API simple.
  
negative.code: '''
  
  [[reactive-change-to-useauthorizationmanager]]
  ==== Change `useAuthorizationManager` to `true`
  
  In Spring Security 5.8, `useAuthorizationManager` was added to {security-api-url}org/springframework/security/config/annotation/method/configuration/EnableReactiveMethodSecurity.html[`@EnableReactiveMethodSecurity`] to allow applications to opt-in to ``AuthorizationManager``'s features.
  
  