anchor.diff:  }
   ----
   
  -The main goal of the `oauth2Login()` DSL was to closely align with the naming as defined in the specifications.
  -
  -The *OAuth 2.0 Authorization Framework* defines the https://tools.ietf.org/html/rfc6749#section-3[Protocol Endpoints] as follows:
  -
  -The authorization process utilizes two authorization server endpoints (HTTP resources):
  -
  -- *Authorization Endpoint* - used by the client to obtain authorization from the resource owner via user-agent redirection.
  -- *Token Endpoint* - used by the client to exchange an authorization grant for an access token, typically with client authentication.
  -
  -As well as one client endpoint:
  -
  -- *Redirection Endpoint* - used by the authorization server to return responses
  -containing authorization credentials to the client via the resource owner user-agent.
  -
  -The *OpenID Connect Core 1.0* specification defines the http://openid.net/specs/openid-connect-core-1_0.html#UserInfo[UserInfo Endpoint] as follows:
  -
  -The *UserInfo Endpoint* is an OAuth 2.0 Protected Resource that returns Claims about the authenticated End-User.
  -To obtain the requested Claims about the End-User, the Client makes a request to the UserInfo Endpoint
  -using an Access Token obtained through OpenID Connect Authentication.
  -These Claims are normally represented by a JSON object that contains a collection of name and value pairs for the Claims.
  -
  -The complete configuration options available for the `oauth2Login()` DSL is as follows:
  +The main goal of the `oauth2Login()` DSL was to closely align with the naming, as defined in the specifications.
  +
  +The OAuth 2.0 Authorization Framework defines the https://tools.ietf.org/html/rfc6749#section-3[Protocol Endpoints].
  +
  +The authorization process uses two authorization server endpoints (HTTP resources):
  +
  +* Authorization Endpoint: Used by the client to obtain authorization from the resource owner through user-agent redirection.
  +* Token Endpoint: Used by the client to exchange an authorization grant for an access token, typically with client authentication.
  +
  +It also uses one client endpoint:
  +
  +* Redirection Endpoint: Used by the authorization server to return responses
  +containing authorization credentials to the client through the resource owner user-agent.
  +
  +The OpenID Connect Core 1.0 specification defines the http://openid.net/specs/openid-connect-core-1_0.html#UserInfo[UserInfo Endpoint] as follows:
  +
  +The UserInfo Endpoint is an OAuth 2.0 Protected Resource that returns claims about the authenticated end-user.
  +To obtain the requested claims about the end-user, the client makes a request to the `UserInfo` endpoint
  +by using an access token obtained through OpenID Connect Authentication.
  +These claims are normally represented by a JSON object that contains a collection of name-value pairs for the claims.
  +
  +The following code shows the complete configuration options available for the `oauth2Login()` DSL:
   
   [source,java]
   ----
  
positive.code: 
  
  [[spring-security-oauth2-core]]
  ===== OAuth 2.0 Core - spring-security-oauth2-core.jar
  Contains core classes and interfaces providing support for the _OAuth 2.0 Authorization Framework_ and _OpenID Connect Core 1.0_. Required by applications leveraging _OAuth 2.0_ and/or _OpenID Connect Core 1.0_, e.g. Client, Resource Server and Authorization Server. The top-level package is `org.springframework.security.oauth2.core`.
  
  
  [[spring-security-oauth2-client]]
  ===== OAuth 2.0 Client - spring-security-oauth2-client.jar
  Spring Security's client support for _OAuth 2.0 Authorization Framework_ and _OpenID Connect Core 1.0_. Required by applications leveraging *OAuth 2.0 Login* and/or OAuth Client support. The top-level package is `org.springframework.security.oauth2.client`.
  
  
  [[spring-security-oauth2-jose]]
  ===== OAuth 2.0 JOSE - spring-security-oauth2-jose.jar
  Spring Security's support for the _JOSE_ framework (Javascript Object Signing and Encryption). The _JOSE_ framework is intended to provide a method to securely transfer claims between parties. It's comprised from a collection of specifications, specifically, JSON Web Token (JWT), JSON Web Signature (JWS), JSON Web Encryption (JWE) and JSON Web Key (JWK). Contains the top-level packages:
  
  * `org.springframework.security.oauth2.jwt`
  
  * `org.springframework.security.oauth2.jose`
  
  
  
negative.code: 
  [IMPORTANT]
  ====
  You also need to ensure the `ClientRegistration.redirectUriTemplate` matches the custom Authorization Response `baseUri`.
  
  The following listing shows an example:
  
  [source,java]
  ----
  