nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Activiti-rest returns 403 forbidden

groopk

When we make an unauthenticated request to activiti-rest, we get a '403 forbidden' response. I believe the correct response should be a 401 unauthorized. This would enable normal rest clients (and web browsers) to properly interact with the basic authentication mechanism of activiti-rest.

Find more posts tagged with

Comments

frederikherema1

That's a coincidence, I stumbled upon that myself this morning when working on the docs for a new and improved REST-API that's coming up. This is indeed not right, as the 403 tells the client to NOT try again because authentication won't help either…

To not break backwards-compatibility with existing clients, the current REST-API will keep returning 403's. The new one, will return 401's as I docked this morning:

Response Description
200 - Ok The operation was successful and a response has been returned (GET and PUT requests).
201 - Created The operation was successful and the entity has been created and is returned in the response-body (POST request).
204 - No content The operation was successful and entity has been deleted and therefor there is no response-body returned (DELETE request).
401 - Unauthorized The operation failed. The operation requires an Authentication header to be set. If this was present in the request, the supplied credentials are not valid or the user is not authorized to perform this operation.
404 - Not found The operation failed.The requested resource was not found.
405 - Method not allowed The operation failed. The used method is not allowed for this resource. Eg. trying to update (PUT) a deployment-resource will result in a 405 status.
409 - Conflict The operation failed. The operation causes an update of a resource that has been updated by another operation, which makes the update no longer valid.
500 - Internal server error The operation failed. An unexpected exception occured while executing the operation. The response-body contains details about the error.