Forbidden (403)¶
If a user tries to access a resource or perform an operation that they do not have permission to, a 403
error will
be returned. For example, calling GET /reports/{id}
where the user does not have READ permission to the report with
this ID, or attempting to submit a report to an enclave the user does not have CREATE permission to, will result in this
error.
In order to mask sensitive details that might be contained in exceptions that can result in a 403
, we replace the error
message with the generic statement, “Could not execute operation due to server error.”
Sample JSON¶
{
"timestamp": 1520959694132,
"status": 403,
"error": "Forbidden",
"message": "Could not execute operation due to server error",
"path": "/api/1.3/reports"
}