OAuth 2.0 endpoint

Endpoint

OAuth 2.0 defines a series of endpoints. T he endpoint is typically a URI on a web server. F or example, a Java Servlet, JSP page, PHP page, ASP. NET web pages and so on.

These endpoint definitions are:

• The authorization endpoint
• Token endpoint
• Redirect the endpoint

Both the authorization endpoint and the token endpoint are on the authorization server, and the redirect endpoint is on the client app. Each endpoint is described below.

These endpoints are illustrated in the following image:

OAuth 2.0 endpoint

The OAuth 2.0 specification does not describe how these endpoints are found or recorded. I t's up to the implementer to decide. Most sites have a subse through which the developer records these endpoints.

The authorization endpoint

The authorization endpoint is the authorized server that the resource owner logs on to and authorizes to the client application.

Token endpoint

The token endpoint is the endpoint on the authorization server for an access token that the client app wants to exchange authorization codes, client identities, and client keys.

Redirect the endpoint

The redirect endpoint is the endpoint that the resource owner is redirected to the client app after the authorization endpoint authorization.