OAuth 2.0 Dynamic Client Registration endpoint

post

Resource for registering clients with the authorization server. See RFC 7591.

Note: Request examples may be rendered as JSON objects, but should be passed in as "application/x-www-form-urlencoded" data types, in accordance with RFC 6749.

options

A pre-flight check generally used for Cross-Origin Resource Sharing (CORS) purposes

OAuth 2.0 Token endpoint

post

Method for requesting OAuth 2.0 Bearer Token (Authorization Code, Client Credentials and Refresh Token grants).

Note: The data flow is dependent on the chosen grant type (e.g. authorization_code, refresh_token, etc.)

Note: Request examples may be rendered as JSON objects, but should be passed in as "application/x-www-form-urlencoded" MIME type, in accordance with RFC 6749.

options

A pre-flight check generally used for Cross-Origin Resource Sharing (CORS) purposes

JSON Web Key Set endpoint

get

Request the JSON Web Keys. See RFC 7517.

OAuth 2.0 Authorization endpoint

get

The client directs the resource owner to this URI, enabling the resource owner to approve the client. See Section 4 of RFC 6749.

post

Means of confirming Resource Owner approval. See RFC 6749.

options

A pre-flight check generally used for Cross-Origin Resource Sharing (CORS) purposes

OAuth 2.0 Token Revocation endpoint (optional)

post

Endpoint for revoking specific Access/Refresh Tokens. See RFC 7009.

options

A pre-flight check generally used for Cross-Origin Resource Sharing (CORS) purposes