@synanetics/types
Version:
Common types for cross repository use
39 lines • 1.96 kB
JavaScript
/**
* Access token error response reasons and their definitions.
*/
export var AccessTokenErrorReason;
(function (AccessTokenErrorReason) {
/**
* The request is missing a parameter so the server can’t proceed with the request. This may also
* be returned if the request includes an unsupported parameter or repeats a parameter.
*/
AccessTokenErrorReason["INVALID_REQUEST"] = "invalid_request";
/**
* Client authentication failed, such as if the request contains an invalid client ID or secret.
* Send an HTTP 401 response in this case.
*/
AccessTokenErrorReason["INVALID_CLIENT"] = "invalid_client";
/**
* The authorization code (or user’s password for the password grant type) is invalid or expired.
* This is also the error you would return if the redirect URL given in the authorization grant
* does not match the URL provided in this access token request.
*/
AccessTokenErrorReason["INVALID_GRANT"] = "invalid_grant";
/**
* For access token requests that include a scope (password or client_credentials grants), this
* error indicates an invalid scope value in the request.
*/
AccessTokenErrorReason["INVALID_SCOPE"] = "invalid_scope";
/**
* This client is not authorized to use the requested grant type. For example, if you restrict
* which applications can use the Implicit grant, you would return this error for the other apps.
*/
AccessTokenErrorReason["UNAUTHORIZED_CLIENT"] = "unauthorized_client";
/**
* If a grant type is requested that the authorization server doesn’t recognize, use this code.
* Note that unknown grant types also use this specific error code rather than using the
* `invalid_request` above.
*/
AccessTokenErrorReason["UNSUPPORTED_GRANT_TYPE"] = "unsupported_grant_type";
})(AccessTokenErrorReason || (AccessTokenErrorReason = {}));
//# sourceMappingURL=accessToken.js.map