You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Kevin Sweeney (JIRA)" <ji...@apache.org> on 2015/03/17 23:49:38 UTC

[jira] [Commented] (AURORA-1187) Create JobKey-scoped Permissions and apply to AuroraSchedulerManager

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

Kevin Sweeney commented on AURORA-1187:
---------------------------------------

https://reviews.apache.org/r/32175/

> Create JobKey-scoped Permissions and apply to AuroraSchedulerManager
> --------------------------------------------------------------------
>
>                 Key: AURORA-1187
>                 URL: https://issues.apache.org/jira/browse/AURORA-1187
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler, Security
>            Reporter: Kevin Sweeney
>            Assignee: Kevin Sweeney
>
> https://reviews.apache.org/r/31820/ added support for coarse-grained permissions based on the thrift API method name. Support finer-grained permissions scoped down to the job
> For example calls to
> {code}
> auroraSchedulerManager.descheduleCronJob(JobKey(role='ksweeney', environment='prod', name='download_lunch_menu'), None, None)
> {code}
> currently check for the {{thrift.AuroraSchedulerManager:descheduleCronJob}} Permission when they should check for the {{thrift.AuroraSchedulerManager:descheduleCronJob:ksweeney:prod:download_lunch_menu}} Permission.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)