[
https://issues.apache.org/jira/browse/GEODE-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191868#comment-16191868
]
ASF subversion and git services commented on GEODE-3621:
--------------------------------------------------------
Commit 8eeb20117c5255be8023e9181caeec268ad082c8 in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8eeb201 ]
GEODE-3621: revert the change to maintain backward compatibility
> Revert breaking changes in SecurityManager
> ------------------------------------------
>
> Key: GEODE-3621
> URL: https://issues.apache.org/jira/browse/GEODE-3621
> Project: Geode
> Issue Type: Bug
> Components: security
> Reporter: Jared Stewart
> Assignee: Patrick Rhomberg
> Fix For: 1.3.0
>
>
> This commit introduced breaking changes to the public SecurityManager API:
> {noformat}
> GEODE-2925: add target for resource operation for finer grained security
> * add finer authorize* call in security service
> * add target to the MXBean authorization check
> * use enum type instead of raw strings for resource/operation
> f541043 Jinmei Liao <[email protected]> on 5/31/17 at 1:50 PM
> committed on 6/12/17 at 11:05 AM
> {noformat}
> Furthermore, using Enum types restricts us from introducing new security
> Resources and Operations in the future. We should revert back to using a
> String-based SecurityManager API to restore backwards compatibility and
> permit future extensibility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
