Mailing-List: contact dev-help@batchee.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@batchee.incubator.apache.org
Date: Sun, 30 Mar 2014 08:39:15 +0000 (UTC)
From: "Romain Manni-Bucau (JIRA)" <jira@apache.org>
To: dev@batchee.incubator.apache.org
Message-ID: <JIRA.12705530.1396168442776.32678.1396168755350@arcas>
In-Reply-To: <JIRA.12705530.1396168442776@arcas>
References: <JIRA.12705530.1396168442776@arcas>
Subject: [jira] [Commented] (BATCHEE-21) Think about security configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Romain Manni-Bucau commented on BATCHEE-21:
-------------------------------------------

Yes I think the config should be a webapp one and not a batchee one. Moreover start/stop... methods of joboperator are secured by spec. So maybe this jira should rather be "propagate security to joboperator from the gui". wdyt?

> Think about security configuration
> ----------------------------------
>
>                 Key: BATCHEE-21
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-21
>             Project: BatchEE
>          Issue Type: Bug
>            Reporter: Mark Struberg
>
> When we use our batchee-servlet jar in a Batch WAR, then everyone can simply start batches. We either want to add some simple IP restriction configuration to our own code, or we shall at least document that one needs to properly secure his batch webapps.


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