anchor.diff:  `NimbusAuthorizationCodeTokenResponseClient` uses the https://connect2id.com/products/nimbus-oauth-openid-connect-sdk[Nimbus OAuth 2.0 SDK] internally.
   
   If you would like to provide a custom implementation of `OAuth2AccessTokenResponseClient`
  -that uses Spring Framework 5 reactive `WebClient` for initiating requests to the token endpoint,
  +that uses Spring Framework 5 reactive `WebClient` for initiating requests to the Token Endpoint,
   configure it as shown in the following example:
   
   [source,java]
  
positive.code: 
  For example, an OAuth Client registered with Okta is assigned to a specific sub-domain and have their own protocol endpoints.
  
  For these cases, Spring Boot 2.0 provides the following base property for configuring custom provider properties: `spring.security.oauth2.client.provider.providerId`.
  
  The following listing shows an example:
  
  
negative.code: Click *Allow* to authorize the OAuth Client to access your email address and basic profile information.
  
  At this point, the OAuth Client retrieves your email address and basic profile information
  from the http://openid.net/specs/openid-connect-core-1_0.html#UserInfo[UserInfo Endpoint] and establishes an authenticated session.
  
  [[jc-oauth2login-client-registration]]
  ==== ClientRegistration
  