1. OAuth 2.0 Tutorial
2. OAuth 2.0 Overview
3. OAuth 2.0 Roles
4. OAuth 2.0 Client Types
5. OAuth 2.0 Authorization
6. OAuth 2.0 Endpoints
7. OAuth 2.0 Requests and Responses
8. OAuth 2.0 Authorization Code Requests and Responses
9. OAuth 2.0 Implicit Requests and Responses
10. OAuth 2.0 Resource Owner Password Credentials Grant - Requests and Response
11. OAuth 2.0 Client Credentials Grant - Requests and Response

• Authorization Endpoint
• Token Endpoint
• Redirect Endpoint

OAuth 2.0 defines a set of endpoints. An endpoint is typically a URI on a web server. For instance, the address of a Java servlet, JSP page, PHP page, ASP.NET page etc.

The endpoints defined are:

• Authorization Endpoint
• Token Endpoint
• Redirection Endpoint

The authorization endpoint and token endpoint are both located on the authorization server. The redirection endpoint is located in the client application. Each of these endpoints are covered below.

The endpoints are illustrated in this diagram:

OAuth 2.0 Endpoints.

The OAuth 2.0 specification does not describe how the URI of these endpoints are found or documented. That is up to each implementer to decide. Most sites will have a subsite for developers documenting these endpoints.

Authorization Endpoint

The authorization endpoint is the endpoint on the authorization server where the resource owner logs in, and grants authorization to the client application.

Token Endpoint

The token endpoint is the endpoint on the authorization server where the client application exchanges the authorization code, client ID and client secret, for an access token.

Redirect Endpoint

The redirect endpoint is the endpoint in the client application where the resource owner is redirected to, after having granted authorization at the authorization endpoint.