anchor.diff:  Testing the method above with `WebTestClient` would require simulating some kind of grant flow with an authorization server.
   Certainly this would be a daunting task, which is why Spring Security ships with support for removing this boilerplate.
   
  -For example, we can tell Spring Security to include a default `OidcUser` using the `SecurityMockServerConfigurers#oidcLogin` method, like so:
  +For example, we can tell Spring Security to include a default `OidcUser` using the `SecurityMockServerConfigurers#mockOidcLogin` method, like so:
   
   ====
   .Java
  
positive.code: ====
  
  Simulating this handshake with the authorization server could be cumbersome.
  Instead, you can use `SecurityMockServerConfigurers#oauth2Client` to add a `OAuth2AuthorizedClient` into a mock `ServerOAuth2AuthorizedClientRepository`:
  
  ====
  .Java
  
negative.code: ----
  ====
  
  In that case, we can tell Spring Security to include a default `BearerTokenAuthentication` using the `SecurityMockServerConfigurers#mockOpaqueToken` method, like so:
  
  ====
  .Java
  