Possible reasons: The authorization grant type is not supported by Hub. Possible reasons: The service that requests authorization token is not verified. Requested scope does not match allowed by access token Provided credentials of the service owner are invalid. Refresh token was issued to another client service.Īuthorization code is unknown or is of invalid format. No service with the provided clientServiceId was found.Īuthorization header was either of invalid format or not passed at all. For example, the client is unknown, no client authentication included, or authentication method is unsupported.

Then check if the request is correct.Ĭlient authentication failed. Also, a parameter in the token request may be mulformed or missing. Possible reasons: Authorization header in response is not of the Bearer type. The request is missing a required parameter, includes an unsupported parameter value (other than grant type), repeats a parameter, includes multiple credentials, utilizes more than one mechanism for authenticating the client, or is otherwise malformed. The scope for which authorization is requested, does not match any registered service.ĭefinition of errors of issuing Access Token in the RFC6749 standard

Try to change selected method of authorization. Hub does not support obtaining an authorization code using this method.

Make sure your service provides at least one redirect_uri in Hub. Make sure the provided redirectUri is correct and properly registered as one of the service's redirect URIs. The client is not authorized to request an authorization code using this method: The redirect_URI of the service either is incorrect or not provided. The authorization request to Hub is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.Ĭheck that all parameters are correct, that provided service_id exists, etc.

Code unknown