[
https://issues.apache.org/jira/browse/JENA-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632797#comment-14632797
]
Claude Warren commented on JENA-990:
------------------------------------
I think OperationDeniedException has at least 3 children
AccessDeniedException -- parent of more specific reasons
AuthenticationRequriedException -- no credentials are available for permissions
assessment.
CannotCreateException -- an existing exception used in a test case but an
example of another case none the less.
AccessDeniedException --parent of
AddDeniedException
DeleteDeniedException
ReadDeniedException
UpdateDeniedException
Fuseki should respond to:
AccessDeniedException with 403 Forbidden - The server understood the request,
but is refusing to fulfill it. Authorization will not help and the request
SHOULD NOT be repeated.
AuthenticationRequiredException with 401 Unauthorized -The request requires
user authentication.
Other OperationDeniedExceptions with 400 Bad Request - The request could not be
understood by the server due to malformed syntax. Though a arguably it could
be a 500 series response.
> rename the UpdateDeniedException
> ---------------------------------
>
> Key: JENA-990
> URL: https://issues.apache.org/jira/browse/JENA-990
> Project: Apache Jena
> Issue Type: Improvement
> Components: Core
> Affects Versions: Jena 3.0.0
> Reporter: Claude Warren
> Assignee: Claude Warren
> Priority: Minor
>
> As noted in a discussion on the dev list between myself and Andy this update
> is to rename the current UpdateDeniedException to AccessDeniedException and
> extend it from a newly created OperationDeniedException.
> AddDeniedException and DeleteDeniedException will extend
> AccessDeniedException.
> jena-permissions will extend AccessDeniedException to create:
> ReadDeniedException -- for read restrictions
> UpdateDeniedException -- for update restrictions (modifying triples that
> already exists as opposed to adding new triples)
> This will allow Fuskei to properly respond to the case where jena-permissions
> is in place and there are update restrictions in place. Currently Fuseki
> returns this as a 500 error. Once we have a common permission denied
> exception we can return either authentication required or access denied as
> appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
