Release Theme | Description | Benefit to users | Apache JIRA# |
---|
Extensibility - Ranger Stacks | Complete re-architecting Ranger to enable new plugins easily | Easily add custom plugins and use Ranger to support multiple datatores | Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | RANGER-203 |
---|
|
|
Hooks for dynamic access control | Users need to support dynamic access control conditions such as geo, time etc | Users can add dynamic rules in addition to static RBAC policy evaluation | Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | RANGER-256 |
---|
|
|
Authorization and auditing support for YARN | Provide ability to manage queue level authorization within Yarn and also audit | Users can manage Yarn ACLs along with other Hadoop component in single UI | Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | RANGER-256 |
---|
|
|
Authorization and auditing support for Kafka | Manage Kafka authorization policies in Ranger and also audit Kafka | Like Yarn, users can manage Kafka security through the centralized security console that other Hadoop components are using | Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | RANGER-246 |
---|
|
|
Audit Optimization | Couple of things - We would want to summarize audit at source, to handle high volume audit scenarios such as in Kafka or HBase
- Include Policy id in the audit logs
| Ranger audit would expand into newer components. With audit summarization, we would be able to manage audit volumes for large event systems like Kafka while still maintaining the traceability required by auditors and compliance teams | Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | RANGER-276 |
---|
|
|
Metadata tags and tag based policies | As complexity of data increases, it is important to classify and tag data it is coming into Hadoop. This feature provides a method to create security policies based on the metadata tags | Users can classify data as "sensitive" or "PII" and then would be able to create policies in Ranger at a tag level. Ranger can then enforce policies for any resources classified under that tag | Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | RANGER-274 |
---|
|
|
| | | |