anchor.diff:  ----
   @EnableMethodSecurity
   ----
  +
  +.Xml
  +[source,xml,role="secondary"]
  +----
  +<method-security/>
  +----
   ====
   
   to:
  
positive.code: ----
  @EnableGlobalMethodSecurity(securedEnabled = true, prePostEnabled = false)
  ----
  ====
  
  === Reactive
  
  ==== Deactivate `AuthorizationManager` in `@EnableReactiveMethodSecurity`
  
  To opt-out of {security-api-url}org/springframework/security/authorization/AuthorizationManager.html[`AuthorizationManager`] for reactive method security, add `useAuthorizationManager = false`:
  
  
negative.code: 
  After updating to 5.8, follow this guide to perform any needed migration steps.
  
  Also, this guide includes ways to <<revert,revert to 5.x>> behaviors and its defaults, should you run into trouble.
  
  == Servlet
  
  === Use `AuthorizationManager` for Method Security
  
  There are no further migration steps for this feature.
  However, if you run into trouble with this enhancement, you can instead <<servlet-replace-methodsecurity-with-globalmethodsecurity,revert the behavior>>.
  
  == Reactive
  
  === Use `AuthorizationManager` for Method Security
  
  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:
  