anchor.diff:  
   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:
  +In 6.0, `@EnableReactiveMethodSecurity` defaults `useAuthorizationManager` to `true`.
  +So, to complete migration, {security-api-url}org/springframework/security/config/annotation/method/configuration/EnableReactiveMethodSecurity.html[`@EnableReactiveMethodSecurity`] remove the `useAuthorizationManager` attribute:
   
   ====
   .Java
  
positive.code: ----
  ====
  
  to:
  
  ====
  .Java
  
negative.code: 
  === Don't Use `AuthorizationManager` in 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.
  
  