anchor.diff:  ----
   ====
   
  -Note that in 6.0, `useAuthorizationManager` defaults to `true`.
  -
  -Additionally, note that `useAuthorizationManager` activates stricter enforcement of Spring Security's non-repeatable or otherwise incompatible annotations.
  +[NOTE]
  +=====
  +In 6.0, `useAuthorizationManager` defaults to `true`.
  +=====
  +
  +'''
  +
  +[[reactive-check-for-annotationconfigurationexceptions]]
  +[%interactive]
  +* [ ] Check for ``AnnotationConfigurationException``s
  +
  +`useAuthorizationManager` activates stricter enforcement of Spring Security's non-repeatable or otherwise incompatible annotations.
   If after turning on `useAuthorizationManager` 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: [source,java,role="primary"]
  ----
  @Bean
  PermissionEvaluator permissionEvaluator() {
  	// ... your evaluator
  }
  ----
  
negative.code: ----
  @EnableMethodSecurity(securedEnabled = true, prePostEnabled = false)
  ----
  
  .Xml
  [source,xml,role="secondary"]
  ----
  <method-security secured-enabled="true" pre-post-enabled="false"/>
  ----
  ====
  
  '''
  
  [[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.
  
  If you have a custom {security-api-url}org/springframework/security/access/PermissionEvaluator.html[`PermissionEvaluator`] `@Bean`, please change it from:
  
  