[jira] [Commented] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
[ https://issues.apache.org/jira/browse/RANGER-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969135#comment-16969135 ] Fatima Amjad Khan commented on RANGER-2635: --- Committed on master [https://github.com/apache/ranger/commit/5ccf414965bff9f79e51738d0bf4ba09880693eb] > Backport hadoop-kms changes in ranger-kms > - > > Key: RANGER-2635 > URL: https://issues.apache.org/jira/browse/RANGER-2635 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2635.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2616) Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs
[ https://issues.apache.org/jira/browse/RANGER-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967501#comment-16967501 ] Fatima Amjad Khan commented on RANGER-2616: --- committed on master [https://github.com/apache/ranger/commit/e5afd844a3020c6c9872481c6dd76a3489dd5c19] > Add reencryptEncryptedKey, batch reencryption interface to KMS and improve > logs > --- > > Key: RANGER-2616 > URL: https://issues.apache.org/jira/browse/RANGER-2616 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.1.0 > > Attachments: 0001-RANGER-2616-v3.patch, 0001-RANGER-2616.patch, > 0001-RANGER-2616_v2.patch, RANGER-2616_v1.patch > > > Currently when an encryption zone (EZ) key is rotated, it only takes effect > on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key > rotation, for improved security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
[ https://issues.apache.org/jira/browse/RANGER-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2635: -- Attachment: (was: 0001-RANGER-2635.patch) > Backport hadoop-kms changes in ranger-kms > - > > Key: RANGER-2635 > URL: https://issues.apache.org/jira/browse/RANGER-2635 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2635.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
[ https://issues.apache.org/jira/browse/RANGER-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2635: -- Attachment: RANGER-2635.patch > Backport hadoop-kms changes in ranger-kms > - > > Key: RANGER-2635 > URL: https://issues.apache.org/jira/browse/RANGER-2635 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2635.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2616) Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs
[ https://issues.apache.org/jira/browse/RANGER-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2616: -- Attachment: 0001-RANGER-2616-v3.patch > Add reencryptEncryptedKey, batch reencryption interface to KMS and improve > logs > --- > > Key: RANGER-2616 > URL: https://issues.apache.org/jira/browse/RANGER-2616 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.1.0 > > Attachments: 0001-RANGER-2616-v3.patch, 0001-RANGER-2616.patch, > 0001-RANGER-2616_v2.patch, RANGER-2616_v1.patch > > > Currently when an encryption zone (EZ) key is rotated, it only takes effect > on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key > rotation, for improved security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
[ https://issues.apache.org/jira/browse/RANGER-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2635: -- Attachment: (was: 0001-RANGER-2635.patch) > Backport hadoop-kms changes in ranger-kms > - > > Key: RANGER-2635 > URL: https://issues.apache.org/jira/browse/RANGER-2635 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: 0001-RANGER-2635.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
[ https://issues.apache.org/jira/browse/RANGER-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2635: -- Attachment: 0001-RANGER-2635.patch > Backport hadoop-kms changes in ranger-kms > - > > Key: RANGER-2635 > URL: https://issues.apache.org/jira/browse/RANGER-2635 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: 0001-RANGER-2635.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
[ https://issues.apache.org/jira/browse/RANGER-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2635: -- Attachment: 0001-RANGER-2635.patch > Backport hadoop-kms changes in ranger-kms > - > > Key: RANGER-2635 > URL: https://issues.apache.org/jira/browse/RANGER-2635 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: 0001-RANGER-2635.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2616) Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs
[ https://issues.apache.org/jira/browse/RANGER-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2616: -- Attachment: 0001-RANGER-2616_v2.patch > Add reencryptEncryptedKey, batch reencryption interface to KMS and improve > logs > --- > > Key: RANGER-2616 > URL: https://issues.apache.org/jira/browse/RANGER-2616 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.1.0 > > Attachments: 0001-RANGER-2616.patch, 0001-RANGER-2616_v2.patch, > RANGER-2616_v1.patch > > > Currently when an encryption zone (EZ) key is rotated, it only takes effect > on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key > rotation, for improved security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2616) Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs
[ https://issues.apache.org/jira/browse/RANGER-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2616: -- Attachment: RANGER-2616_v1.patch > Add reencryptEncryptedKey, batch reencryption interface to KMS and improve > logs > --- > > Key: RANGER-2616 > URL: https://issues.apache.org/jira/browse/RANGER-2616 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.1.0 > > Attachments: 0001-RANGER-2616.patch, RANGER-2616_v1.patch > > > Currently when an encryption zone (EZ) key is rotated, it only takes effect > on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key > rotation, for improved security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2635) Backport hadoop-kms changes in ranger-kms
Fatima Amjad Khan created RANGER-2635: - Summary: Backport hadoop-kms changes in ranger-kms Key: RANGER-2635 URL: https://issues.apache.org/jira/browse/RANGER-2635 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949162#comment-16949162 ] Fatima Amjad Khan commented on RANGER-2589: --- Committed on master [https://github.com/apache/ranger/commit/3f468bab324b78de86e1efa38bb823c685c2b077] > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589-v3.patch, 0001-RANGER-2589-v4.patch, > RANGER-2589-v1.patch, RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2616) Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs
[ https://issues.apache.org/jira/browse/RANGER-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2616: -- Description: Currently when an encryption zone (EZ) key is rotated, it only takes effect on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key rotation, for improved security. > Add reencryptEncryptedKey, batch reencryption interface to KMS and improve > logs > --- > > Key: RANGER-2616 > URL: https://issues.apache.org/jira/browse/RANGER-2616 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Currently when an encryption zone (EZ) key is rotated, it only takes effect > on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key > rotation, for improved security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2616) Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs
Fatima Amjad Khan created RANGER-2616: - Summary: Add reencryptEncryptedKey, batch reencryption interface to KMS and improve logs Key: RANGER-2616 URL: https://issues.apache.org/jira/browse/RANGER-2616 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: 0001-RANGER-2589-v4.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589-v3.patch, 0001-RANGER-2589-v4.patch, > RANGER-2589-v1.patch, RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: (was: RANGER-2589-v3.patch) > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589-v3.patch, RANGER-2589-v1.patch, > RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: (was: 0001-RANGER-2589.patch) > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589-v3.patch, RANGER-2589-v1.patch, > RANGER-2589-v2.patch, RANGER-2589-v3.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: 0001-RANGER-2589-v3.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589-v3.patch, 0001-RANGER-2589.patch, > RANGER-2589-v1.patch, RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: (was: RANGER-2589-v2.patch) > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch, RANGER-2589-v1.patch, > RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: RANGER-2589-v2.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch, RANGER-2589-v1.patch, > RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (RANGER-2597) Allow auditor role user to get details of services and policies from public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944479#comment-16944479 ] Fatima Amjad Khan edited comment on RANGER-2597 at 10/4/19 1:07 PM: Committed on master [https://github.com/apache/ranger/commit/9a62c142ac7dbd7d3412076c26787c2d2e9ec1c6]] was (Author: fatimaawez): Committed on [master|[https://github.com/apache/ranger/commit/9a62c142ac7dbd7d3412076c26787c2d2e9ec1c6]] > Allow auditor role user to get details of services and policies from public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2597.patch > > > Allow auditor role user to get details of services and policies from public > API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2597) Allow auditor role user to get details of services and policies from public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944479#comment-16944479 ] Fatima Amjad Khan commented on RANGER-2597: --- Committed on [master|[https://github.com/apache/ranger/commit/9a62c142ac7dbd7d3412076c26787c2d2e9ec1c6]] > Allow auditor role user to get details of services and policies from public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2597.patch > > > Allow auditor role user to get details of services and policies from public > API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: RANGER-2589-v2.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch, RANGER-2589-v1.patch, > RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: (was: RANGER-2589-v2.patch) > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch, RANGER-2589-v1.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: RANGER-2589-v2.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch, RANGER-2589-v1.patch, > RANGER-2589-v2.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: RANGER-2589-v1.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch, RANGER-2589-v1.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2589: -- Attachment: 0001-RANGER-2589.patch > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > Attachments: 0001-RANGER-2589.patch > > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2589) Introduce Ranger API to return Ranger's JVM resource status metric
[ https://issues.apache.org/jira/browse/RANGER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan reassigned RANGER-2589: - Assignee: Fatima Amjad Khan (was: Pradeep Agrawal) > Introduce Ranger API to return Ranger's JVM resource status metric > -- > > Key: RANGER-2589 > URL: https://issues.apache.org/jira/browse/RANGER-2589 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Minor > > Important JVM attributes can be returned via Ranger REST API : > * heap memory usage > * GC time > * # of open threads > * # of open file descriptors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of services and policies from public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Attachment: RANGER-2597.patch > Allow auditor role user to get details of services and policies from public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2597.patch > > > Allow auditor role user to get details of services and policies from public > API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of Services and Policies from public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Summary: Allow auditor role user to get details of Services and Policies from public API (was: Allow auditor role user to get details of Services and Policies in public API) > Allow auditor role user to get details of Services and Policies from public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Allow auditor role user to get details of Services and Policies in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of Services and Policies from public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Description: Allow auditor role user to get details of services and policies from public API (was: Allow auditor role user to get details of Services and Policies in public API) > Allow auditor role user to get details of Services and Policies from public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Allow auditor role user to get details of services and policies from public > API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of services and policies from public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Summary: Allow auditor role user to get details of services and policies from public API (was: Allow auditor role user to get details of Services and Policies from public API) > Allow auditor role user to get details of services and policies from public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Allow auditor role user to get details of services and policies from public > API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of Services and Policies in public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Description: Allow auditor role user to get details of Services and Policies in public API (was: Allow auditor role user to access the get API's in public API) > Allow auditor role user to get details of Services and Policies in public API > -- > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Allow auditor role user to get details of Services and Policies in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of Services and Policies in public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Summary: Allow auditor role user to get details of Services and Policies in public API (was: Allow auditor role user to access the services and policy details in public API) > Allow auditor role user to get details of Services and Policies in public API > -- > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Allow auditor role user to access the get API's in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to get details of Services and Policies in public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Attachment: (was: RANGER-2597.patch) > Allow auditor role user to get details of Services and Policies in public API > -- > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > > Allow auditor role user to access the get API's in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to access the services and polices details in public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Summary: Allow auditor role user to access the services and polices details in public API (was: Allow auditor role user to access the get API's in public API) > Allow auditor role user to access the services and polices details in public > API > > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2597.patch > > > Allow auditor role user to access the get API's in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to access the services and policy details in public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Summary: Allow auditor role user to access the services and policy details in public API (was: Allow auditor role user to access the services and polices details in public API) > Allow auditor role user to access the services and policy details in public > API > --- > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2597.patch > > > Allow auditor role user to access the get API's in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2597) Allow auditor role user to access the get API's in public API
[ https://issues.apache.org/jira/browse/RANGER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2597: -- Attachment: RANGER-2597.patch > Allow auditor role user to access the get API's in public API > - > > Key: RANGER-2597 > URL: https://issues.apache.org/jira/browse/RANGER-2597 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2597.patch > > > Allow auditor role user to access the get API's in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2597) Allow auditor role user to access the get API's in public API
Fatima Amjad Khan created RANGER-2597: - Summary: Allow auditor role user to access the get API's in public API Key: RANGER-2597 URL: https://issues.apache.org/jira/browse/RANGER-2597 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan Allow auditor role user to access the get API's in public API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2570) Handling the pop up of policy details on Ranger Access audit log row
[ https://issues.apache.org/jira/browse/RANGER-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934379#comment-16934379 ] Fatima Amjad Khan commented on RANGER-2570: --- Closing this issue as its handled in https://issues.apache.org/jira/browse/RANGER-2580 > Handling the pop up of policy details on Ranger Access audit log row > > > Key: RANGER-2570 > URL: https://issues.apache.org/jira/browse/RANGER-2570 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2570.patch, RANGER-2570_v1.patch > > > Issue on pop up of policy details of ranger access audit log row -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2570) Handling the pop up of policy details on Ranger Access audit log row
[ https://issues.apache.org/jira/browse/RANGER-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2570: -- Attachment: RANGER-2570_v1.patch > Handling the pop up of policy details on Ranger Access audit log row > > > Key: RANGER-2570 > URL: https://issues.apache.org/jira/browse/RANGER-2570 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2570.patch, RANGER-2570_v1.patch > > > Issue on pop up of policy details of ranger access audit log row -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2570) Handling the pop up of policy details on Ranger Access audit log row
[ https://issues.apache.org/jira/browse/RANGER-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2570: -- Description: Issue on pop up of policy details of ranger access audit log row > Handling the pop up of policy details on Ranger Access audit log row > > > Key: RANGER-2570 > URL: https://issues.apache.org/jira/browse/RANGER-2570 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2570.patch > > > Issue on pop up of policy details of ranger access audit log row -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2570) Handling the pop up of policy details on Ranger Access audit log row
[ https://issues.apache.org/jira/browse/RANGER-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2570: -- Attachment: RANGER-2570.patch > Handling the pop up of policy details on Ranger Access audit log row > > > Key: RANGER-2570 > URL: https://issues.apache.org/jira/browse/RANGER-2570 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2570.patch > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (RANGER-2570) Handling the pop up of policy details on Ranger Access audit log row
Fatima Amjad Khan created RANGER-2570: - Summary: Handling the pop up of policy details on Ranger Access audit log row Key: RANGER-2570 URL: https://issues.apache.org/jira/browse/RANGER-2570 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.0.0 Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: (was: 0001-RANGER-2490.patch) > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: 0001-RANGER-2490.patch > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: 0001-RANGER-2490.patch > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: (was: 0001-RANGER-2490.patch) > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: 0001-RANGER-2490.patch > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: (was: 0001-RANGER-2490.patch) > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2490) Add https support while using Solr API to upload config set
[ https://issues.apache.org/jira/browse/RANGER-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2490: -- Attachment: 0001-RANGER-2490.patch > Add https support while using Solr API to upload config set > --- > > Key: RANGER-2490 > URL: https://issues.apache.org/jira/browse/RANGER-2490 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2490.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2482) Ranger: use Solr API to upload config set (during bootstrapping)
[ https://issues.apache.org/jira/browse/RANGER-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2482: -- Attachment: RANGER-2482.patch > Ranger: use Solr API to upload config set (during bootstrapping) > > > Key: RANGER-2482 > URL: https://issues.apache.org/jira/browse/RANGER-2482 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2482.patch > > > Ranger: > - remove ZK znode check > - remove ZK config set upload > - remove ZK acl set > - use Solr config set API > ([https://lucene.apache.org/solr/guide/7_4/config-sets.html]) to upload the > config sets (only if it does not exists ... also probably Solr4J should have > this call) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2482) Ranger: use Solr API to upload config set (during bootstrapping)
Fatima Amjad Khan created RANGER-2482: - Summary: Ranger: use Solr API to upload config set (during bootstrapping) Key: RANGER-2482 URL: https://issues.apache.org/jira/browse/RANGER-2482 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan Fix For: master Ranger: - remove ZK znode check - remove ZK config set upload - remove ZK acl set - use Solr config set API ([https://lucene.apache.org/solr/guide/7_4/config-sets.html]) to upload the config sets (only if it does not exists ... also probably Solr4J should have this call) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2114) Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'content' at row 1
[
https://issues.apache.org/jira/browse/RANGER-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579682#comment-16579682
]
Fatima Amjad Khan commented on RANGER-2114:
---
Committed on [Master|
https://github.com/apache/ranger/commit/ecbc7a66f124395f9ddf42d0a60d4ead9e6e0542]
> Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data
> too long for column 'content' at row 1
>
>
> Key: RANGER-2114
> URL: https://issues.apache.org/jira/browse/RANGER-2114
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Alexander Posledov
>Assignee: Fatima Amjad Khan
>Priority: Major
> Attachments: RANGER-2114.patch
>
>
> An attempt to delete a service definition ends with:
>
> {code:java}
> // Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation:
> Data too long for column 'content' at row 1
> Error Code: 1406
> Call: INSERT INTO x_data_hist (action, content, CREATE_TIME, from_time,
> obj_class_type, obj_guid, obj_id, obj_name, to_time, UPDATE_TIME, version)
> VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> bind = [11 parameters bound]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2114) Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'content' at row 1
[
https://issues.apache.org/jira/browse/RANGER-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fatima Amjad Khan updated RANGER-2114:
--
Attachment: RANGER-2114.patch
> Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data
> too long for column 'content' at row 1
>
>
> Key: RANGER-2114
> URL: https://issues.apache.org/jira/browse/RANGER-2114
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Alexander Posledov
>Assignee: Fatima Amjad Khan
>Priority: Major
> Attachments: RANGER-2114.patch
>
>
> An attempt to delete a service definition ends with:
>
> {code:java}
> // Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation:
> Data too long for column 'content' at row 1
> Error Code: 1406
> Call: INSERT INTO x_data_hist (action, content, CREATE_TIME, from_time,
> obj_class_type, obj_guid, obj_id, obj_name, to_time, UPDATE_TIME, version)
> VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> bind = [11 parameters bound]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (RANGER-2114) Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'content' at row 1
[
https://issues.apache.org/jira/browse/RANGER-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fatima Amjad Khan reassigned RANGER-2114:
-
Assignee: Fatima Amjad Khan
> Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data
> too long for column 'content' at row 1
>
>
> Key: RANGER-2114
> URL: https://issues.apache.org/jira/browse/RANGER-2114
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Alexander Posledov
>Assignee: Fatima Amjad Khan
>Priority: Major
>
> An attempt to delete a service definition ends with:
>
> {code:java}
> // Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation:
> Data too long for column 'content' at row 1
> Error Code: 1406
> Call: INSERT INTO x_data_hist (action, content, CREATE_TIME, from_time,
> obj_class_type, obj_guid, obj_id, obj_name, to_time, UPDATE_TIME, version)
> VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> bind = [11 parameters bound]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2138) Add unit tests for org.apache.ranger.service package
[ https://issues.apache.org/jira/browse/RANGER-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558050#comment-16558050 ] Fatima Amjad Khan edited comment on RANGER-2138 at 7/26/18 8:38 AM: Committed on [master|https://github.com/apache/ranger/commit/d352dfaab216eb7c2a1abef5b689aa993430a549] Committed on [ranger-1| https://github.com/apache/ranger/commit/a75510f4fc03c9672c7846d50540c372a3e0d252] Committed on [ranger-1.1| https://github.com/apache/ranger/commit/6e9e42e7c96c88d72eed1cf8b0a65071fbc509a5] was (Author: fatimaawez): Committed on [master|https://github.com/apache/ranger/commit/d352dfaab216eb7c2a1abef5b689aa993430a549] > Add unit tests for org.apache.ranger.service package > > > Key: RANGER-2138 > URL: https://issues.apache.org/jira/browse/RANGER-2138 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2138.patch, RANGER-2138_v2.patch > > > Add unit tests for org.apache.ranger.service package -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2138) Add unit tests for org.apache.ranger.service package
[ https://issues.apache.org/jira/browse/RANGER-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2138: -- Attachment: RANGER-2138_v2.patch > Add unit tests for org.apache.ranger.service package > > > Key: RANGER-2138 > URL: https://issues.apache.org/jira/browse/RANGER-2138 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2138.patch, RANGER-2138_v2.patch > > > Add unit tests for org.apache.ranger.service package -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2138) Add unit tests for org.apache.ranger.service package
[ https://issues.apache.org/jira/browse/RANGER-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520040#comment-16520040 ] Fatima Amjad Khan commented on RANGER-2138: --- Committed on [master| https://github.com/apache/ranger/commit/29fedc53fdc4a9df9f5857e754cf6fdcad488cef] > Add unit tests for org.apache.ranger.service package > > > Key: RANGER-2138 > URL: https://issues.apache.org/jira/browse/RANGER-2138 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2138.patch > > > Add unit tests for org.apache.ranger.service package -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2138) Add unit tests for org.apache.ranger.service package
[ https://issues.apache.org/jira/browse/RANGER-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2138: -- Attachment: RANGER-2138.patch > Add unit tests for org.apache.ranger.service package > > > Key: RANGER-2138 > URL: https://issues.apache.org/jira/browse/RANGER-2138 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2138.patch > > > Add unit tests for org.apache.ranger.service package -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2138) Add unit tests for org.apache.ranger.service package
[ https://issues.apache.org/jira/browse/RANGER-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2138: -- Attachment: (was: RANGER-2138.patch) > Add unit tests for org.apache.ranger.service package > > > Key: RANGER-2138 > URL: https://issues.apache.org/jira/browse/RANGER-2138 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2138.patch > > > Add unit tests for org.apache.ranger.service package -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2138) Add unit tests for org.apache.ranger.service package
[ https://issues.apache.org/jira/browse/RANGER-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2138: -- Attachment: RANGER-2138.patch > Add unit tests for org.apache.ranger.service package > > > Key: RANGER-2138 > URL: https://issues.apache.org/jira/browse/RANGER-2138 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Attachments: RANGER-2138.patch > > > Add unit tests for org.apache.ranger.service package -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500033#comment-16500033 ] Fatima Amjad Khan commented on RANGER-2113: --- Committed on [master| https://github.com/apache/ranger/commit/987abe8064529b08149a03ab22e2dbfbbe1cc0d8] > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2113.patch > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2113: -- Attachment: RANGER-2113.patch > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2113.patch > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2113: -- Attachment: (was: RANGER-2113.patch) > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2113.patch > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2113: -- Attachment: RANGER-2113.patch > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2113.patch > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2113: -- Attachment: (was: RANGER-2113.patch) > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2113: -- Attachment: RANGER-2113.patch > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2113.patch > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2113) Improve error handling when of change password process gets killed.
[ https://issues.apache.org/jira/browse/RANGER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2113: -- Attachment: RANGER-2113.patch > Improve error handling when of change password process gets killed. > --- > > Key: RANGER-2113 > URL: https://issues.apache.org/jira/browse/RANGER-2113 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2113.patch > > > Improve error handling when of change password process gets killed by exiting > the setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2106) Keyadmin is not able to see 'Audit tab' and 'User tab' by default.
[ https://issues.apache.org/jira/browse/RANGER-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483449#comment-16483449 ] Fatima Amjad Khan commented on RANGER-2106: --- Committed on [master| https://github.com/apache/ranger/commit/0ff82bcad230ae9e58220c587218972213f593c6] > Keyadmin is not able to see 'Audit tab' and 'User tab' by default. > -- > > Key: RANGER-2106 > URL: https://issues.apache.org/jira/browse/RANGER-2106 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2106.patch > > > Keyadmin is not able to see audit and user tab by default when consolidated > db schema executes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2106) Keyadmin is not able to see 'Audit tab' and 'User tab' by default.
[ https://issues.apache.org/jira/browse/RANGER-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2106: -- Attachment: RANGER-2106.patch > Keyadmin is not able to see 'Audit tab' and 'User tab' by default. > -- > > Key: RANGER-2106 > URL: https://issues.apache.org/jira/browse/RANGER-2106 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: master > > Attachments: RANGER-2106.patch > > > Keyadmin is not able to see audit and user tab by default when consolidated > db schema executes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2106) Keyadmin is not able to see 'Audit tab' and 'User tab' by default.
Fatima Amjad Khan created RANGER-2106: - Summary: Keyadmin is not able to see 'Audit tab' and 'User tab' by default. Key: RANGER-2106 URL: https://issues.apache.org/jira/browse/RANGER-2106 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan Fix For: master Keyadmin is not able to see audit and user tab by default when consolidated db schema executes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
[ https://issues.apache.org/jira/browse/RANGER-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476803#comment-16476803 ] Fatima Amjad Khan commented on RANGER-2100: --- Committed on [master| https://github.com/apache/ranger/commit/626f92a9226ea6938578b7d18c3ee7bd835c958e] > REST API to get count of total services, policies, users, groups and various > mapping > > > Key: RANGER-2100 > URL: https://issues.apache.org/jira/browse/RANGER-2100 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2100.patch > > > This API will get the details analytics for the following > * Count of Services created for each type of service > * Number of policies by Service Type along with Service Name: # of resource > policies, tag-based policies, masking policies, row filtering policies > * Number of Audit Events by Service Type: size of solr index, number of > denial events and number of access events > * Number of groups and users synced > * Policy DB type and version: MySQL, Oracle.. > * Context enrichers: Number and type used. > * Count of Deny conditions for resources. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
[ https://issues.apache.org/jira/browse/RANGER-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2100: -- Attachment: (was: RANGER-2100.patch) > REST API to get count of total services, policies, users, groups and various > mapping > > > Key: RANGER-2100 > URL: https://issues.apache.org/jira/browse/RANGER-2100 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2100.patch > > > This API will get the details analytics for the following > * Count of Services created for each type of service > * Number of policies by Service Type along with Service Name: # of resource > policies, tag-based policies, masking policies, row filtering policies > * Number of Audit Events by Service Type: size of solr index, number of > denial events and number of access events > * Number of groups and users synced > * Policy DB type and version: MySQL, Oracle.. > * Context enrichers: Number and type used. > * Count of Deny conditions for resources. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
[ https://issues.apache.org/jira/browse/RANGER-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2100: -- Attachment: RANGER-2100.patch > REST API to get count of total services, policies, users, groups and various > mapping > > > Key: RANGER-2100 > URL: https://issues.apache.org/jira/browse/RANGER-2100 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2100.patch > > > This API will get the details analytics for the following > * Count of Services created for each type of service > * Number of policies by Service Type along with Service Name: # of resource > policies, tag-based policies, masking policies, row filtering policies > * Number of Audit Events by Service Type: size of solr index, number of > denial events and number of access events > * Number of groups and users synced > * Policy DB type and version: MySQL, Oracle.. > * Context enrichers: Number and type used. > * Count of Deny conditions for resources. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
[ https://issues.apache.org/jira/browse/RANGER-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2100: -- Attachment: RANGER-2100.patch > REST API to get count of total services, policies, users, groups and various > mapping > > > Key: RANGER-2100 > URL: https://issues.apache.org/jira/browse/RANGER-2100 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2100.patch > > > This API will get the details analytics for the following > * Count of Services created for each type of service > * Number of policies by Service Type along with Service Name: # of resource > policies, tag-based policies, masking policies, row filtering policies > * Number of Audit Events by Service Type: size of solr index, number of > denial events and number of access events > * Number of groups and users synced > * Policy DB type and version: MySQL, Oracle.. > * Context enrichers: Number and type used. > * Count of Deny conditions for resources. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
[ https://issues.apache.org/jira/browse/RANGER-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2100: -- Description: This API will get the details analytics for the following * Count of Services created for each type of service * Number of policies by Service Type along with Service Name: # of resource policies, tag-based policies, masking policies, row filtering policies * Number of Audit Events by Service Type: size of solr index, number of denial events and number of access events * Number of groups and users synced * Policy DB type and version: MySQL, Oracle.. * Context enrichers: Number and type used. * Count of Deny conditions for resources. was: This API wil get the details analytics for the following * Count of Services created for each type of service * Number of policies by Service Type along with Service Name: # of resource policies, tag-based policies, masking policies, row filtering policies * Number of Audit Events by Service Type: size of solr index, number of denial events and number of access events * Number of groups and users synced * Policy DB type and version: MySQL, Oracle.. * Context enrichers: Number and type used. * Count of Deny conditions for resources. > REST API to get count of total services, policies, users, groups and various > mapping > > > Key: RANGER-2100 > URL: https://issues.apache.org/jira/browse/RANGER-2100 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > > This API will get the details analytics for the following > * Count of Services created for each type of service > * Number of policies by Service Type along with Service Name: # of resource > policies, tag-based policies, masking policies, row filtering policies > * Number of Audit Events by Service Type: size of solr index, number of > denial events and number of access events > * Number of groups and users synced > * Policy DB type and version: MySQL, Oracle.. > * Context enrichers: Number and type used. > * Count of Deny conditions for resources. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
[ https://issues.apache.org/jira/browse/RANGER-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2100: -- Description: This API wil get the details analytics for the following * Count of Services created for each type of service * Number of policies by Service Type along with Service Name: # of resource policies, tag-based policies, masking policies, row filtering policies * Number of Audit Events by Service Type: size of solr index, number of denial events and number of access events * Number of groups and users synced * Policy DB type and version: MySQL, Oracle.. * Context enrichers: Number and type used. * Count of Deny conditions for resources. was:This API wil get the Count of usergroups, policies, services, contextenrichers, audits, database. > REST API to get count of total services, policies, users, groups and various > mapping > > > Key: RANGER-2100 > URL: https://issues.apache.org/jira/browse/RANGER-2100 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Pradeep Agrawal >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > > This API wil get the details analytics for the following > * Count of Services created for each type of service > * Number of policies by Service Type along with Service Name: # of resource > policies, tag-based policies, masking policies, row filtering policies > * Number of Audit Events by Service Type: size of solr index, number of > denial events and number of access events > * Number of groups and users synced > * Policy DB type and version: MySQL, Oracle.. > * Context enrichers: Number and type used. > * Count of Deny conditions for resources. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2100) REST API to get count of total services, policies, users, groups and various mapping
Fatima Amjad Khan created RANGER-2100: - Summary: REST API to get count of total services, policies, users, groups and various mapping Key: RANGER-2100 URL: https://issues.apache.org/jira/browse/RANGER-2100 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan Fix For: master This API wil get the Count of usergroups, policies, services, contextenrichers, audits, database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2083) Restrict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468632#comment-16468632 ] Fatima Amjad Khan commented on RANGER-2083: --- Committed to [master| https://github.com/apache/ranger/commit/cccb5e1b949e843f6ff756f2019938d65125ea08] > Restrict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2083.patch > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2083) Restrict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2083: -- Attachment: (was: RANGER-2083.patch) > Restrict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2083.patch > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2083) Restrict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2083: -- Attachment: RANGER-2083.patch > Restrict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2083.patch > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2083) Restrict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2083: -- Attachment: RANGER-2083.patch > Restrict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2083.patch > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2083) Restrict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2083: -- Summary: Restrict KMS audit events to KMS related users only (was: Resctict KMS audit events to KMS related users only ) > Restrict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2083) Restrict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2083: -- Attachment: (was: RANGER-2083.patch) > Restrict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2041) Handle validations for passwords of admin accounts during ranger install.
[ https://issues.apache.org/jira/browse/RANGER-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460550#comment-16460550 ] Fatima Amjad Khan commented on RANGER-2041: --- Committed the v2 patch on [master| https://github.com/apache/ranger/commit/2b9f76e818e404ae824b40479f6c3cb84d870a92] > Handle validations for passwords of admin accounts during ranger install. > - > > Key: RANGER-2041 > URL: https://issues.apache.org/jira/browse/RANGER-2041 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.0.1 > > Attachments: RANGER-2041.patch, RANGER-2041_V2.patch > > > Currently, when Ranger is installed admin,keyadmin, rangerusersync, > rangertagsync users are seeded users and they are configurable during the > install process. This task is to provide a facility to add validations to the > admin users password during ranger install. Python doesn’t support ‘ ` “ \ so > these characters will not be supported during update of default password of > seeded users in manual install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2083) Resctict KMS audit events to KMS related users only
[ https://issues.apache.org/jira/browse/RANGER-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2083: -- Attachment: RANGER-2083.patch > Resctict KMS audit events to KMS related users only > > > Key: RANGER-2083 > URL: https://issues.apache.org/jira/browse/RANGER-2083 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: master > > Attachments: RANGER-2083.patch > > > Only Keyadmin and KMS Auditor role users should be able to see KMS related > audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2083) Resctict KMS audit events to KMS related users only
Fatima Amjad Khan created RANGER-2083: - Summary: Resctict KMS audit events to KMS related users only Key: RANGER-2083 URL: https://issues.apache.org/jira/browse/RANGER-2083 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Fatima Amjad Khan Assignee: Fatima Amjad Khan Fix For: master Only Keyadmin and KMS Auditor role users should be able to see KMS related audit logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2041) Handle validations for passwords of admin accounts during ranger install.
[ https://issues.apache.org/jira/browse/RANGER-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2041: -- Attachment: RANGER-2041_V2.patch > Handle validations for passwords of admin accounts during ranger install. > - > > Key: RANGER-2041 > URL: https://issues.apache.org/jira/browse/RANGER-2041 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.0.1 > > Attachments: RANGER-2041.patch, RANGER-2041_V2.patch > > > Currently, when Ranger is installed admin,keyadmin, rangerusersync, > rangertagsync users are seeded users and they are configurable during the > install process. This task is to provide a facility to add validations to the > admin users password during ranger install. Python doesn’t support ‘ ` “ \ so > these characters will not be supported during update of default password of > seeded users in manual install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2070) Ranger Storm service creation fails
[
https://issues.apache.org/jira/browse/RANGER-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445358#comment-16445358
]
Fatima Amjad Khan commented on RANGER-2070:
---
Committed on
[master|https://github.com/apache/ranger/commit/1eeedee82c66f54eb73d5bfe2f9d0c707facb1ff]
> Ranger Storm service creation fails
> ---
>
> Key: RANGER-2070
> URL: https://issues.apache.org/jira/browse/RANGER-2070
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: master
>Reporter: Fatima Amjad Khan
>Assignee: Fatima Amjad Khan
>Priority: Major
> Fix For: master
>
> Attachments: RANGER-2070.patch
>
>
> {code:java}
> In latest ranger when tried to enable plugin for Storm, ranger service
> creation fails.
> Found below in Ranger-Admin logs.
> 2018-04-07 09:48:53,132 [http-bio-6080-exec-4] INFO
> apache.ranger.security.web.filter.RangerKRBAuthenticationFilter
> (RangerKRBAuthenticationFilter.java:220) - Logged into Ranger as =
> storm-rangerstorm
> 2018-04-07 09:48:53,136 [http-bio-6080-exec-4] INFO
> org.apache.ranger.common.RESTErrorUtil (RESTErrorUtil.java:84) - Request
> failed. loginId=null, logMessage=Bad Credentials
> javax.ws.rs.WebApplicationException
> at
> org.apache.ranger.common.RESTErrorUtil.generateRESTException(RESTErrorUtil.java:77)
> at
> org.apache.ranger.biz.RangerBizUtil.blockAuditorRoleUser(RangerBizUtil.java:1637)
> at org.apache.ranger.biz.UserMgr.addUserRole(UserMgr.java:981)
> at org.apache.ranger.biz.UserMgr.createUser(UserMgr.java:167)
> at
> org.apache.ranger.biz.UserMgr$$FastClassBySpringCGLIB$$3bbcf0cf.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
> at
> org.apache.ranger.biz.UserMgr$$EnhancerBySpringCGLIB$$f11ad8ab.createUser()
> at
> org.apache.ranger.biz.XUserMgr.createServiceConfigUser(XUserMgr.java:2225)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2070) Ranger Storm service creation fails
[
https://issues.apache.org/jira/browse/RANGER-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fatima Amjad Khan updated RANGER-2070:
--
Attachment: RANGER-2070.patch
> Ranger Storm service creation fails
> ---
>
> Key: RANGER-2070
> URL: https://issues.apache.org/jira/browse/RANGER-2070
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: master
>Reporter: Fatima Amjad Khan
>Assignee: Fatima Amjad Khan
>Priority: Major
> Fix For: master
>
> Attachments: RANGER-2070.patch
>
>
> {code:java}
> In latest ranger when tried to enable plugin for Storm, ranger service
> creation fails.
> Found below in Ranger-Admin logs.
> 2018-04-07 09:48:53,132 [http-bio-6080-exec-4] INFO
> apache.ranger.security.web.filter.RangerKRBAuthenticationFilter
> (RangerKRBAuthenticationFilter.java:220) - Logged into Ranger as =
> storm-rangerstorm
> 2018-04-07 09:48:53,136 [http-bio-6080-exec-4] INFO
> org.apache.ranger.common.RESTErrorUtil (RESTErrorUtil.java:84) - Request
> failed. loginId=null, logMessage=Bad Credentials
> javax.ws.rs.WebApplicationException
> at
> org.apache.ranger.common.RESTErrorUtil.generateRESTException(RESTErrorUtil.java:77)
> at
> org.apache.ranger.biz.RangerBizUtil.blockAuditorRoleUser(RangerBizUtil.java:1637)
> at org.apache.ranger.biz.UserMgr.addUserRole(UserMgr.java:981)
> at org.apache.ranger.biz.UserMgr.createUser(UserMgr.java:167)
> at
> org.apache.ranger.biz.UserMgr$$FastClassBySpringCGLIB$$3bbcf0cf.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
> at
> org.apache.ranger.biz.UserMgr$$EnhancerBySpringCGLIB$$f11ad8ab.createUser()
> at
> org.apache.ranger.biz.XUserMgr.createServiceConfigUser(XUserMgr.java:2225)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2070) Ranger Storm service creation fails
Fatima Amjad Khan created RANGER-2070:
-
Summary: Ranger Storm service creation fails
Key: RANGER-2070
URL: https://issues.apache.org/jira/browse/RANGER-2070
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: master
Reporter: Fatima Amjad Khan
Assignee: Fatima Amjad Khan
Fix For: master
{code:java}
In latest ranger when tried to enable plugin for Storm, ranger service creation
fails.
Found below in Ranger-Admin logs.
2018-04-07 09:48:53,132 [http-bio-6080-exec-4] INFO
apache.ranger.security.web.filter.RangerKRBAuthenticationFilter
(RangerKRBAuthenticationFilter.java:220) - Logged into Ranger as =
storm-rangerstorm
2018-04-07 09:48:53,136 [http-bio-6080-exec-4] INFO
org.apache.ranger.common.RESTErrorUtil (RESTErrorUtil.java:84) - Request
failed. loginId=null, logMessage=Bad Credentials
javax.ws.rs.WebApplicationException
at
org.apache.ranger.common.RESTErrorUtil.generateRESTException(RESTErrorUtil.java:77)
at
org.apache.ranger.biz.RangerBizUtil.blockAuditorRoleUser(RangerBizUtil.java:1637)
at org.apache.ranger.biz.UserMgr.addUserRole(UserMgr.java:981)
at org.apache.ranger.biz.UserMgr.createUser(UserMgr.java:167)
at
org.apache.ranger.biz.UserMgr$$FastClassBySpringCGLIB$$3bbcf0cf.invoke()
at
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
at
org.apache.ranger.biz.UserMgr$$EnhancerBySpringCGLIB$$f11ad8ab.createUser()
at
org.apache.ranger.biz.XUserMgr.createServiceConfigUser(XUserMgr.java:2225)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (RANGER-2041) Handle validations for passwords of admin accounts during ranger install.
[ https://issues.apache.org/jira/browse/RANGER-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan reopened RANGER-2041: --- > Handle validations for passwords of admin accounts during ranger install. > - > > Key: RANGER-2041 > URL: https://issues.apache.org/jira/browse/RANGER-2041 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.0.1 > > Attachments: RANGER-2041.patch > > > Currently, when Ranger is installed admin,keyadmin, rangerusersync, > rangertagsync users are seeded users and they are configurable during the > install process. This task is to provide a facility to add validations to the > admin users password during ranger install. Python doesn’t support ‘ ` “ \ so > these characters will not be supported during update of default password of > seeded users in manual install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2041) Handle validations for passwords of admin accounts during ranger install.
[ https://issues.apache.org/jira/browse/RANGER-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430126#comment-16430126 ] Fatima Amjad Khan commented on RANGER-2041: --- Committed on [master |https://github.com/apache/ranger/commit/c8f67ce7c9314867b6481ee10e82ed19b15f37e8 ] > Handle validations for passwords of admin accounts during ranger install. > - > > Key: RANGER-2041 > URL: https://issues.apache.org/jira/browse/RANGER-2041 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.0.1 > > Attachments: RANGER-2041.patch > > > Currently, when Ranger is installed admin,keyadmin, rangerusersync, > rangertagsync users are seeded users and they are configurable during the > install process. This task is to provide a facility to add validations to the > admin users password during ranger install. Python doesn’t support ‘ ` “ \ so > these characters will not be supported during update of default password of > seeded users in manual install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2041) Handle validations for passwords of admin accounts during ranger install.
[ https://issues.apache.org/jira/browse/RANGER-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2041: -- Attachment: RANGER-2041.patch > Handle validations for passwords of admin accounts during ranger install. > - > > Key: RANGER-2041 > URL: https://issues.apache.org/jira/browse/RANGER-2041 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.0.1 > > Attachments: RANGER-2041.patch > > > Currently, when Ranger is installed admin,keyadmin, rangerusersync, > rangertagsync users are seeded users and they are configurable during the > install process. This task is to provide a facility to add validations to the > admin users password during ranger install. Python doesn’t support ‘ ` “ \ so > these characters will not be supported during update of default password of > seeded users in manual install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2041) Handle validations for passwords of admin accounts during ranger install.
[ https://issues.apache.org/jira/browse/RANGER-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2041: -- Attachment: (was: RANGER-2041.patch) > Handle validations for passwords of admin accounts during ranger install. > - > > Key: RANGER-2041 > URL: https://issues.apache.org/jira/browse/RANGER-2041 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.0.1 > > Attachments: RANGER-2041.patch > > > Currently, when Ranger is installed admin,keyadmin, rangerusersync, > rangertagsync users are seeded users and they are configurable during the > install process. This task is to provide a facility to add validations to the > admin users password during ranger install. Python doesn’t support ‘ ` “ \ so > these characters will not be supported during update of default password of > seeded users in manual install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2039) Allow access to Audit tab for all users of role Keyadmin and KMS Auditor
[ https://issues.apache.org/jira/browse/RANGER-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2039: -- Affects Version/s: master > Allow access to Audit tab for all users of role Keyadmin and KMS Auditor > - > > Key: RANGER-2039 > URL: https://issues.apache.org/jira/browse/RANGER-2039 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master, 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: master, 1.1.0 > > Attachments: RANGER-2039.patch > > > Currently by default users having Keyadmin or KMS auditor role doesn't get > access to Audits tab in Ranger UI, but ideally it should have audit access > right so that when we login through keyadmin and KMS Auditor we should be > able to view the KMS related audits and user/groups tab. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2039) Allow access to Audit tab for all users of role Keyadmin and KMS Auditor
[ https://issues.apache.org/jira/browse/RANGER-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-2039: -- Fix Version/s: master > Allow access to Audit tab for all users of role Keyadmin and KMS Auditor > - > > Key: RANGER-2039 > URL: https://issues.apache.org/jira/browse/RANGER-2039 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master, 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: master, 1.1.0 > > Attachments: RANGER-2039.patch > > > Currently by default users having Keyadmin or KMS auditor role doesn't get > access to Audits tab in Ranger UI, but ideally it should have audit access > right so that when we login through keyadmin and KMS Auditor we should be > able to view the KMS related audits and user/groups tab. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2039) Allow access to Audit tab for all users of role Keyadmin and KMS Auditor
[ https://issues.apache.org/jira/browse/RANGER-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425376#comment-16425376 ] Fatima Amjad Khan commented on RANGER-2039: --- Committed on [master|https://github.com/apache/ranger/commit/57e01bab63a5d4972886954399e8e4fc240d4431] > Allow access to Audit tab for all users of role Keyadmin and KMS Auditor > - > > Key: RANGER-2039 > URL: https://issues.apache.org/jira/browse/RANGER-2039 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master, 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: master, 1.1.0 > > Attachments: RANGER-2039.patch > > > Currently by default users having Keyadmin or KMS auditor role doesn't get > access to Audits tab in Ranger UI, but ideally it should have audit access > right so that when we login through keyadmin and KMS Auditor we should be > able to view the KMS related audits and user/groups tab. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2040) Improvement in Analytics Metric of Ranger Admin and Ranger Kms for Users/groups metric collection for Auditor Role.
[ https://issues.apache.org/jira/browse/RANGER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425374#comment-16425374 ] Fatima Amjad Khan commented on RANGER-2040: --- Committed on [master|https://github.com/apache/ranger/commit/27d6453a935e0f1aa36184fc34e05ca7c4045fa7] > Improvement in Analytics Metric of Ranger Admin and Ranger Kms for > Users/groups metric collection for Auditor Role. > --- > > Key: RANGER-2040 > URL: https://issues.apache.org/jira/browse/RANGER-2040 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.1 >Reporter: Fatima Amjad Khan >Assignee: Fatima Amjad Khan >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2040.patch > > > Improvement in Analytics Metric of Ranger Admin and Ranger Kms for > Users/groups metric collection for Auditor Role. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
