aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1737) Descheduling a cron job checks role access before job key existence
Date Wed, 01 Feb 2017 07:54:54 GMT

     [ https://issues.apache.org/jira/browse/AURORA-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephan Erb updated AURORA-1737:
--------------------------------
    Fix Version/s: 0.17.0

> Descheduling a cron job checks role access before job key existence
> -------------------------------------------------------------------
>
>                 Key: AURORA-1737
>                 URL: https://issues.apache.org/jira/browse/AURORA-1737
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: Joshua Cohen
>            Assignee: Jing Chen
>            Priority: Minor
>             Fix For: 0.17.0
>
>
> Trying to deschedule a cron job for a non-existent role returns a permission error rather
than a no-such-job error. This leads to confusion for users in the event of a typo in the
role.
> Given that jobs are world-readable, we should check for a valid job key before applying
permissions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message