geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1673) SampleSecurityManager should cause start to fail if security.json cannot be found
Date Mon, 25 Jul 2016 18:02:20 GMT

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

ASF subversion and git services commented on GEODE-1673:
--------------------------------------------------------

Commit 8812d540372786cdd6dc664574effb38123e3292 in incubator-geode's branch refs/heads/feature/GEODE-1673-PR-212
from [~gmeilen]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8812d54 ]

GEODE-1673: fail start if security.json cannot be found

* collapse JSONAuthorization into SampleSecurityManager
* update SampleSecurityManager to support file, resource and string json
* cleanup security tests
* add SecurityTest category to security tests

This closes #212


> SampleSecurityManager should cause start to fail if security.json cannot be found
> ---------------------------------------------------------------------------------
>
>                 Key: GEODE-1673
>                 URL: https://issues.apache.org/jira/browse/GEODE-1673
>             Project: Geode
>          Issue Type: Bug
>          Components: security
>            Reporter: Kirk Lund
>            Assignee: Grace Meilen
>
> When following the instructions on https://cwiki.apache.org/confluence/display/GEODE/Using+Custom+SecurityManager,
if the user forgets to specify "--classpath=." then the locator will start up but cannot be
connected to.
> The SampleSecurityManager should instead cause the start to fail if security.json cannot
be found.



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

Mime
View raw message