geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-17) Provide Integrated Security
Date Wed, 18 May 2016 17:05:13 GMT


ASF subversion and git services commented on GEODE-17:

Commit 1179c08eb4f9d1fe1c1ffea337a34a0f1c6c89c7 in incubator-geode's branch refs/heads/feature/GEODE-1392
from [~jinmeiliao]
[;h=1179c08 ]

GEODE-17: make geode authorization case-sensitive since our region names are case sensitive

* Specify case sensitive when creating the permission context
* Specify case sensitive when resolving the permission from shiro-ini file
* rename shiro-init to security-shiro-init since it's security related in DistributionConfig
* For DATA operations, a "NULL" regionName is used when regionName couldn't be resolved yet.
Since for permissions,
  DATA:READ is different from DATA:READ:NULL

> Provide Integrated Security
> ---------------------------
>                 Key: GEODE-17
>                 URL:
>             Project: Geode
>          Issue Type: New Feature
>          Components: client/server, docs, security
>            Reporter: Tushar Khairnar
>            Assignee: Jens Deppe
>              Labels: security
> Integrated Security: Purpose of integrated security feature is to provide uniform authentication
and authorization capabilities for all Geode clients. Geode distributed systems has different
clients, some perform cache/region operations, some perform management operations. In order
to authenticate and authorize these actions we need single consistent framework or interface.
Such interface should allow configuration of access levels from single place and/or repository.

> The key requirements being met here are
>  - Authentication of all clients from single plugin
>  - Authorization of cache/data operations (through cache-client and REST) and managements
(GFSH/JMX) operations from single plugin
>  - Extend existing Client-Server security framework

This message was sent by Atlassian JIRA

View raw message