You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/08/08 19:49:12 UTC

[jira] [Commented] (FALCON-466) REST APIs must add the entity owner as an implicit filter

    [ https://issues.apache.org/jira/browse/FALCON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091028#comment-14091028 ] 

Venkatesh Seetharam commented on FALCON-466:
--------------------------------------------

[~bvellanki], why is this dependent on FALCON-470, FALCON-471, FALCON-472, and FALCON-473?

> REST APIs must add the entity owner as an implicit filter
> ---------------------------------------------------------
>
>                 Key: FALCON-466
>                 URL: https://issues.apache.org/jira/browse/FALCON-466
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: webapp
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>            Assignee: Balu Vellanki
>              Labels: authorization, security
>             Fix For: 0.6
>
>         Attachments: Falcon-Jira-466.v2.patch
>
>
> Implement authorization for entity actions. Entity created by one user should not be updated/deleted by another user. Entity operations will only apply for the entities owned by that user.
> Entity and instance operations must add the authenticated user/owner as an implicit filter so the user operates on only his entities. For example: List will return entities belonging to the authenticated user, lifecycle operations such as delete/kill/suspend/resume/etc. are only applicable to the owner of the entity. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)