RESTlets and REST Web Services Authentication Errors
The following table lists WWW-Authenticate response header errors that may occur when RESTlets and REST web services are authenticated.
Error Value |
Error_description Value |
Error Description |
---|---|---|
invalid_request |
The request could not be understood by the server due to malformed syntax. |
The request is in a wrong format. One or more parameters are missing, repeated, or malformed. The HTTP status code is 400 Bad Request. |
invalid_token |
Invalid login attempt. |
The provided access token is expired, revoked, malformed, or invalid. The HTTP status code is 401 Unauthorized. |
The following examples show headers for the errors in the preceding table:
HTTP/1.1 400 Bad Request
WWW-Authenticate: Bearer realm="123456",
error="invalid_request",
error_description="The request could not be understood by the server due to malformed syntax."
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="123456",
error="invalid_token",
error_description="Invalid login attempt."
Note:
The value of the realm is the account ID for which the data are requested.