anchor.diff:  
   === Don't Use `AuthorizationManager` in Method Security
   
  -[[servlet-replace-methodsecurity-with-globalmethodsecurity]]
  -[%interactive]
  -* [ ] Replace xref:servlet/authorization/method-security.adoc#jc-enable-method-security[method security] with xref:servlet/authorization/method-security.adoc#jc-enable-global-method-security[global method security]
  +To opt out of `AuthorizationManager` for Method Security, replace xref:servlet/authorization/method-security.adoc#jc-enable-method-security[method security] with xref:servlet/authorization/method-security.adoc#jc-enable-global-method-security[global method security]
   
   For applications using xref:servlet/authorization/method-security.adoc#jc-enable-method-security[pre-post annotations], make sure to turn it on to reactivate the behavior.
   
  
positive.code: 
  If you run into trouble with this enhancement, you can instead <<reactive-change-to-useauthorizationmanager-false,revert the behavior>>.
  
  [[reactive-method-security-remove-useauthorizationmanager]]
  [%interactive]
  * [ ] Remove `useAuthorizationManager` usage from `@EnableReactiveMethodSecurity`
  
  {security-api-url}org/springframework/security/config/annotation/method/configuration/EnableReactiveMethodSecurity.html[`@EnableReactiveMethodSecurity`] sets `useAuthorizationManager` to `true` by default.
  Because of that, in 6.0 you can change:
  
  ====
  .Java
  
negative.code: ----
  ====
  
  changes to:
  
  ====
  .Java
  