[jira] [Commented] (RANGER-4258) Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum service definitions, services, and zones.
[ https://issues.apache.org/jira/browse/RANGER-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17728240#comment-17728240 ] Nitin Galave commented on RANGER-4258: -- [~madhan] Thanks > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum service definitions, services, and zones. > --- > > Key: RANGER-4258 > URL: https://issues.apache.org/jira/browse/RANGER-4258 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Minor > Fix For: 3.0.0 > > > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum (at least 1000) service definitions, services, > and zones. > cc: [~mad...@apache.org] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4258) Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum service definitions, services, and zones.
[ https://issues.apache.org/jira/browse/RANGER-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-4258: - Description: Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum (at least 1000) service definitions, services, and zones. cc: [~mad...@apache.org] was:Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum (at least 1000) service definitions, services, and zones. > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum service definitions, services, and zones. > --- > > Key: RANGER-4258 > URL: https://issues.apache.org/jira/browse/RANGER-4258 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Minor > > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum (at least 1000) service definitions, services, > and zones. > cc: [~mad...@apache.org] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4258) Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum service definitions, services, and zones.
[ https://issues.apache.org/jira/browse/RANGER-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727870#comment-17727870 ] Nitin Galave commented on RANGER-4258: -- [~Dhaval.Rajpara] Please review https://reviews.apache.org/r/74458/ > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum service definitions, services, and zones. > --- > > Key: RANGER-4258 > URL: https://issues.apache.org/jira/browse/RANGER-4258 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Minor > > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum (at least 1000) service definitions, services, > and zones. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4258) Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum service definitions, services, and zones.
[ https://issues.apache.org/jira/browse/RANGER-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727870#comment-17727870 ] Nitin Galave edited comment on RANGER-4258 at 5/31/23 9:11 AM: --- [~Dhaval.Rajpara] [~mad...@apache.org] Please review https://reviews.apache.org/r/74458/ was (Author: nitin.galave): [~Dhaval.Rajpara] Please review https://reviews.apache.org/r/74458/ > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum service definitions, services, and zones. > --- > > Key: RANGER-4258 > URL: https://issues.apache.org/jira/browse/RANGER-4258 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Minor > > Ranger: Instead of limiting the listing to only 25, Ranger should provide a > comprehensive list of maximum (at least 1000) service definitions, services, > and zones. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4258) Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum service definitions, services, and zones.
Nitin Galave created RANGER-4258: Summary: Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum service definitions, services, and zones. Key: RANGER-4258 URL: https://issues.apache.org/jira/browse/RANGER-4258 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave Ranger: Instead of limiting the listing to only 25, Ranger should provide a comprehensive list of maximum (at least 1000) service definitions, services, and zones. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3991) Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js
[ https://issues.apache.org/jira/browse/RANGER-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685694#comment-17685694 ] Nitin Galave edited comment on RANGER-3991 at 2/8/23 5:55 AM: -- Committed to [master|https://github.com/apache/ranger/commit/67ff6f0b6908db0ff9ac2f9c98be5ebdaf0b5941] and [ranger-2.4|https://github.com/apache/ranger/commit/8d472998396e1095313c1c73fd067c5eca0b186a ] branch. cc: [~Dhaval.Rajpara] was (Author: nitin.galave): Committed to [master|https://github.com/apache/ranger/commit/67ff6f0b6908db0ff9ac2f9c98be5ebdaf0b5941] and [ranger-2.4|https://github.com/apache/ranger/commit/8d472998396e1095313c1c73fd067c5eca0b186a ] branch. > Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js > --- > > Key: RANGER-3991 > URL: https://issues.apache.org/jira/browse/RANGER-3991 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Bhavik Patel >Assignee: Himanshu Maurya >Priority: Critical > Attachments: > 0001-RANGER-3991-Upgrade-underscore-min.js-underscore.js--1.patch, > 0001-RANGER-3991-Upgrade-underscore-min.js-underscore.js-.patch, > 0001-RANGER-3991.patch > > > Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js > > cc : [~Dhaval.Rajpara] [~ni3galave] [~chenyu] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3991) Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js
[ https://issues.apache.org/jira/browse/RANGER-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685694#comment-17685694 ] Nitin Galave edited comment on RANGER-3991 at 2/8/23 5:54 AM: -- Committed to [master|https://github.com/apache/ranger/commit/67ff6f0b6908db0ff9ac2f9c98be5ebdaf0b5941] and [ranger-2.4|https://github.com/apache/ranger/commit/8d472998396e1095313c1c73fd067c5eca0b186a ] branch. was (Author: nitin.galave): Committed to [master|https://github.com/apache/ranger/commit/67ff6f0b6908db0ff9ac2f9c98be5ebdaf0b5941]and [ranger-2.4|https://github.com/apache/ranger/commit/8d472998396e1095313c1c73fd067c5eca0b186a ]branch. > Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js > --- > > Key: RANGER-3991 > URL: https://issues.apache.org/jira/browse/RANGER-3991 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Bhavik Patel >Assignee: Himanshu Maurya >Priority: Critical > Attachments: > 0001-RANGER-3991-Upgrade-underscore-min.js-underscore.js--1.patch, > 0001-RANGER-3991-Upgrade-underscore-min.js-underscore.js-.patch, > 0001-RANGER-3991.patch > > > Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js > > cc : [~Dhaval.Rajpara] [~ni3galave] [~chenyu] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3991) Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js
[ https://issues.apache.org/jira/browse/RANGER-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685694#comment-17685694 ] Nitin Galave commented on RANGER-3991: -- Committed to [master|https://github.com/apache/ranger/commit/67ff6f0b6908db0ff9ac2f9c98be5ebdaf0b5941]and [ranger-2.4|https://github.com/apache/ranger/commit/8d472998396e1095313c1c73fd067c5eca0b186a ]branch. > Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js > --- > > Key: RANGER-3991 > URL: https://issues.apache.org/jira/browse/RANGER-3991 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Bhavik Patel >Assignee: Himanshu Maurya >Priority: Critical > Attachments: > 0001-RANGER-3991-Upgrade-underscore-min.js-underscore.js--1.patch, > 0001-RANGER-3991-Upgrade-underscore-min.js-underscore.js-.patch, > 0001-RANGER-3991.patch > > > Upgrade underscore-min.js, underscore.js and moment-with-locales.min.js > > cc : [~Dhaval.Rajpara] [~ni3galave] [~chenyu] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4028) Ranger - Upgrade bootbox.js.
[ https://issues.apache.org/jira/browse/RANGER-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682414#comment-17682414 ] Nitin Galave commented on RANGER-4028: -- Committed to [master|https://github.com/apache/ranger/commit/fdc88c907cc0693341b17f7c119cdc2603980a27] and [ranger-2.4|https://github.com/apache/ranger/commit/7c34c0857ea8a55b05374b5d794bc61832dee2b6] branch. > Ranger - Upgrade bootbox.js. > > > Key: RANGER-4028 > URL: https://issues.apache.org/jira/browse/RANGER-4028 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4028.patch > > > Ranger - Upgrade bootbox.js version 5.4.0 to 5.5.3. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3901) Upgrade jquery-ui to 1.13.2
[ https://issues.apache.org/jira/browse/RANGER-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612554#comment-17612554 ] Nitin Galave commented on RANGER-3901: -- Committed to : master : https://github.com/apache/ranger/commit/ce033d82fd6915cfc0b48e49680b395a885cef64 ranger-2.4 : https://github.com/apache/ranger/commit/ba0c019d8d8d141fd343e3a2e10259c3149f1cd4 > Upgrade jquery-ui to 1.13.2 > --- > > Key: RANGER-3901 > URL: https://issues.apache.org/jira/browse/RANGER-3901 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-3901.patch > > > Upgrade jquery-ui to 1.13.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-3804) Update policy UI to support multiple resource-sets
[ https://issues.apache.org/jira/browse/RANGER-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave resolved RANGER-3804. -- Resolution: Fixed > Update policy UI to support multiple resource-sets > -- > > Key: RANGER-3804 > URL: https://issues.apache.org/jira/browse/RANGER-3804 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0, 2.4.0 > > Attachments: > 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch, > EntityID.png, classification.png, entity-label.png > > > Policy model enhancements in RANGER_3796 enable a Ranger policy to be created > with multiple resource-sets – like: > * database: [ db1 ], table: [ tbl1 ], column: [ * ] > * database: [ db1 ], udf: [ * ] > * database: [ db2 ], table: [ tbl2 ], column: [ * ] > > Policy UI needs to be updated to support multiple resource-sets, some what > similar to security-zone UI that allows multiple resource-sets to be added in > a zone. For policy UI, I suggest retaining existing UI for > RangerPolicy.resources, and have a separate optional UI (triggered via _More > Resources_ button?) to capture additional resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (RANGER-3804) Update policy UI to support multiple resource-sets
[ https://issues.apache.org/jira/browse/RANGER-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave reopened RANGER-3804: -- > Update policy UI to support multiple resource-sets > -- > > Key: RANGER-3804 > URL: https://issues.apache.org/jira/browse/RANGER-3804 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0, 2.4.0 > > Attachments: > 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch, > EntityID.png, classification.png, entity-label.png > > > Policy model enhancements in RANGER_3796 enable a Ranger policy to be created > with multiple resource-sets – like: > * database: [ db1 ], table: [ tbl1 ], column: [ * ] > * database: [ db1 ], udf: [ * ] > * database: [ db2 ], table: [ tbl2 ], column: [ * ] > > Policy UI needs to be updated to support multiple resource-sets, some what > similar to security-zone UI that allows multiple resource-sets to be added in > a zone. For policy UI, I suggest retaining existing UI for > RangerPolicy.resources, and have a separate optional UI (triggered via _More > Resources_ button?) to capture additional resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3804) Update policy UI to support multiple resource-sets
[ https://issues.apache.org/jira/browse/RANGER-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3804: - Attachment: (was: 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch) > Update policy UI to support multiple resource-sets > -- > > Key: RANGER-3804 > URL: https://issues.apache.org/jira/browse/RANGER-3804 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Nitin Galave >Priority: Major > Attachments: > 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch, > EntityID.png, classification.png, entity-label.png > > > Policy model enhancements in RANGER_3796 enable a Ranger policy to be created > with multiple resource-sets – like: > * database: [ db1 ], table: [ tbl1 ], column: [ * ] > * database: [ db1 ], udf: [ * ] > * database: [ db2 ], table: [ tbl2 ], column: [ * ] > > Policy UI needs to be updated to support multiple resource-sets, some what > similar to security-zone UI that allows multiple resource-sets to be added in > a zone. For policy UI, I suggest retaining existing UI for > RangerPolicy.resources, and have a separate optional UI (triggered via _More > Resources_ button?) to capture additional resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3804) Update policy UI to support multiple resource-sets
[ https://issues.apache.org/jira/browse/RANGER-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3804: - Attachment: 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch > Update policy UI to support multiple resource-sets > -- > > Key: RANGER-3804 > URL: https://issues.apache.org/jira/browse/RANGER-3804 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Nitin Galave >Priority: Major > Attachments: > 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch, > EntityID.png, classification.png, entity-label.png > > > Policy model enhancements in RANGER_3796 enable a Ranger policy to be created > with multiple resource-sets – like: > * database: [ db1 ], table: [ tbl1 ], column: [ * ] > * database: [ db1 ], udf: [ * ] > * database: [ db2 ], table: [ tbl2 ], column: [ * ] > > Policy UI needs to be updated to support multiple resource-sets, some what > similar to security-zone UI that allows multiple resource-sets to be added in > a zone. For policy UI, I suggest retaining existing UI for > RangerPolicy.resources, and have a separate optional UI (triggered via _More > Resources_ button?) to capture additional resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3804) Update policy UI to support multiple resource-sets
[ https://issues.apache.org/jira/browse/RANGER-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3804: - Attachment: 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch > Update policy UI to support multiple resource-sets > -- > > Key: RANGER-3804 > URL: https://issues.apache.org/jira/browse/RANGER-3804 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Nitin Galave >Priority: Major > Attachments: > 0001-RANGER-3804-Update-policy-UI-to-support-multiple-res.patch, > EntityID.png, classification.png, entity-label.png > > > Policy model enhancements in RANGER_3796 enable a Ranger policy to be created > with multiple resource-sets – like: > * database: [ db1 ], table: [ tbl1 ], column: [ * ] > * database: [ db1 ], udf: [ * ] > * database: [ db2 ], table: [ tbl2 ], column: [ * ] > > Policy UI needs to be updated to support multiple resource-sets, some what > similar to security-zone UI that allows multiple resource-sets to be added in > a zone. For policy UI, I suggest retaining existing UI for > RangerPolicy.resources, and have a separate optional UI (triggered via _More > Resources_ button?) to capture additional resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3648) Alt-text hover-over for long policy names
[ https://issues.apache.org/jira/browse/RANGER-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519326#comment-17519326 ] Nitin Galave commented on RANGER-3648: -- This looks good > Alt-text hover-over for long policy names > - > > Key: RANGER-3648 > URL: https://issues.apache.org/jira/browse/RANGER-3648 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Ryan Jendoubi >Priority: Minor > Attachments: image-2022-02-28-16-00-58-330.png, > image-2022-02-28-16-02-46-830.png > > > *As a* user of the Ranger UI > *I want* to see the full names of policies without clicking in to them, even > if the names are quite long > *So that* I don't have to navigate or open modal dialogs to differentiate > policies with long names which may begin the same way. > This is often achieved in other software by using the browser's built-in > behaviour for alt tags to make a simple "pop up" when the element is hovered > over. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (RANGER-3328) RANGER-KMS : code improvement
[ https://issues.apache.org/jira/browse/RANGER-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave reassigned RANGER-3328: Assignee: Mateen Mansoori > RANGER-KMS : code improvement > - > > Key: RANGER-3328 > URL: https://issues.apache.org/jira/browse/RANGER-3328 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Mateen N Mansoori >Assignee: Mateen Mansoori >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > > The following Hadoop kms changes need to be ported in ranger-kms : > [HADOOP-14784|https://issues.apache.org/jira/browse/HADOOP-14784], > [HADOOP-15234|https://issues.apache.org/jira/browse/HADOOP-15234], > [HADOOP-15455|https://issues.apache.org/jira/browse/HADOOP-15455], > [HADOOP-15418|https://issues.apache.org/jira/browse/HADOOP-15418], > RangerKeyStoreProvider : remove duplicate check. > RangerHSM : improve null check -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (RANGER-3487) Update underscorejs with latest version.
[ https://issues.apache.org/jira/browse/RANGER-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486500#comment-17486500 ] Nitin Galave commented on RANGER-3487: -- Committed to [apache-master|https://github.com/apache/ranger/commit/26401a9024b6e02389a87c4700eccf0a7b96302b] branch. Committed to [ranger-2.3|https://github.com/apache/ranger/commit/2fac8c94813b672390516fe86d9174d5d16299a0] branch. > Update underscorejs with latest version. > > > Key: RANGER-3487 > URL: https://issues.apache.org/jira/browse/RANGER-3487 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3487.patch > > > For more functionality update underscorejs with the latest version is 1.13.1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3487) Update underscorejs with latest version.
[ https://issues.apache.org/jira/browse/RANGER-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3487: - Attachment: 0001-RANGER-3487.patch > Update underscorejs with latest version. > > > Key: RANGER-3487 > URL: https://issues.apache.org/jira/browse/RANGER-3487 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3487.patch > > > For more functionality update underscorejs with the latest version is 1.13.1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3487) Update underscorejs with latest version.
Nitin Galave created RANGER-3487: Summary: Update underscorejs with latest version. Key: RANGER-3487 URL: https://issues.apache.org/jira/browse/RANGER-3487 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave For more functionality update underscorejs with the latest version is 1.13.1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3443) "X-Permitted-Cross-Domain-Policies" header not set by Ranger UI
[
https://issues.apache.org/jira/browse/RANGER-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3443:
-
Attachment: 0001-RANGER-3443.patch
> "X-Permitted-Cross-Domain-Policies" header not set by Ranger UI
> ---
>
> Key: RANGER-3443
> URL: https://issues.apache.org/jira/browse/RANGER-3443
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Nitin Galave
>Assignee: Nitin Galave
>Priority: Major
> Attachments: 0001-RANGER-3443.patch
>
>
> Ranger does not return "X-Permitted-Cross-Domain-Policies" response header.
> OWASP best practices suggest explicitly setting this header to "none":
> {code:java}
> X-Permitted-Cross-Domain-Policies: none{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3463) Use apt logger to log messages
[ https://issues.apache.org/jira/browse/RANGER-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3463: - Fix Version/s: 3.0.0 > Use apt logger to log messages > -- > > Key: RANGER-3463 > URL: https://issues.apache.org/jira/browse/RANGER-3463 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Mateen Mansoori >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-3463-Use-apt-logger-to-log-messages.patch > > > Avoid use of System.out.println in KMSMetricUtil.java at line numbers 74, 79, > 98, 104. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3457: - Affects Version/s: (was: 2.2.0) > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0 > > Attachments: 0002-RANGER-3457.patch, 0003-RANGER-3457.patch > > > 1) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed > 2) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 40 sec and restarted > Ranger > 2. Open Ranger UI on an incognito window with hrt_qa/Password@123 > 3. Didnt perform any operation / mouse operation for 4 mins > *Issue:* > Idle logout wizard (with "logout now" and "stay logged in" is not shown) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3457: - Fix Version/s: (was: 2.2.0) > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0 > > Attachments: 0002-RANGER-3457.patch, 0003-RANGER-3457.patch > > > 1) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed > 2) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 40 sec and restarted > Ranger > 2. Open Ranger UI on an incognito window with hrt_qa/Password@123 > 3. Didnt perform any operation / mouse operation for 4 mins > *Issue:* > Idle logout wizard (with "logout now" and "stay logged in" is not shown) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424423#comment-17424423 ] Nitin Galave commented on RANGER-3457: -- Committed to [apache-master|https://github.com/apache/ranger/commit/d7a3de193d45f00ef20ef8859d025b444b2dba0b] branch. > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: 0002-RANGER-3457.patch, 0003-RANGER-3457.patch > > > 1) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed > 2) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 40 sec and restarted > Ranger > 2. Open Ranger UI on an incognito window with hrt_qa/Password@123 > 3. Didnt perform any operation / mouse operation for 4 mins > *Issue:* > Idle logout wizard (with "logout now" and "stay logged in" is not shown) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3461) [Session Timeout-Ranger-multi-tab] After selecting "stay signed in" other ranger UI tabs never encounters timeout even after configured idle timeout value
[
https://issues.apache.org/jira/browse/RANGER-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3461:
-
Description:
Steps:
# Configure ranger.service.inactivity.timeout=40 and restart ranger
# Open the ranger UI link on an incognito window on 3 tabs
# Be idle for 35 secs
# On one of the tab click "stay signed in" (on other tabs timer stops and
popup wizard got closed)
# Be idle for another 40 secs
{color:#de350b}*Issue:*{color}
1) Only that tab where "stay signed in" button clicked in above 4th step
session timeout happened and in other tabs session timeout doesnt happen.
2) Difference in Ranger and Atlas UI behaviour with multiple tabs and session
idle timeout
was:
Steps:
# Configure ranger.service.inactivity.timeout=40 and restart ranger
# Open the ranger UI link on an incognito window on 3 tabs
# Be idle for 35 secs
# On one of the tab click "stay signed in" (on other tabs timer stops and
popup wizard got closed)
# Be idle for another 40 secs
{color:#de350b}*Issue:*{color}
Only that tab where "stay signed in" button clicked in above 4th step session
timeout happened and in other tabs session timeout doesnt happen
> [Session Timeout-Ranger-multi-tab] After selecting "stay signed in" other
> ranger UI tabs never encounters timeout even after configured idle timeout
> value
> --
>
> Key: RANGER-3461
> URL: https://issues.apache.org/jira/browse/RANGER-3461
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Nitin Galave
>Assignee: Nitin Galave
>Priority: Major
>
> Steps:
> # Configure ranger.service.inactivity.timeout=40 and restart ranger
> # Open the ranger UI link on an incognito window on 3 tabs
> # Be idle for 35 secs
> # On one of the tab click "stay signed in" (on other tabs timer stops and
> popup wizard got closed)
> # Be idle for another 40 secs
> {color:#de350b}*Issue:*{color}
> 1) Only that tab where "stay signed in" button clicked in above 4th step
> session timeout happened and in other tabs session timeout doesnt happen.
> 2) Difference in Ranger and Atlas UI behaviour with multiple tabs and
> session idle timeout
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3461) [Session Timeout-Ranger-multi-tab] After selecting "stay signed in" other ranger UI tabs never encounters timeout even after configured idle timeout value
Nitin Galave created RANGER-3461:
Summary: [Session Timeout-Ranger-multi-tab] After selecting "stay
signed in" other ranger UI tabs never encounters timeout even after configured
idle timeout value
Key: RANGER-3461
URL: https://issues.apache.org/jira/browse/RANGER-3461
Project: Ranger
Issue Type: Improvement
Components: Ranger
Reporter: Nitin Galave
Assignee: Nitin Galave
Steps:
# Configure ranger.service.inactivity.timeout=40 and restart ranger
# Open the ranger UI link on an incognito window on 3 tabs
# Be idle for 35 secs
# On one of the tab click "stay signed in" (on other tabs timer stops and
popup wizard got closed)
# Be idle for another 40 secs
{color:#de350b}*Issue:*{color}
Only that tab where "stay signed in" button clicked in above 4th step session
timeout happened and in other tabs session timeout doesnt happen
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3457: - Attachment: 0003-RANGER-3457.patch > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: 0002-RANGER-3457.patch, 0003-RANGER-3457.patch > > > 1) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed > 2) > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 40 sec and restarted > Ranger > 2. Open Ranger UI on an incognito window with hrt_qa/Password@123 > 3. Didnt perform any operation / mouse operation for 4 mins > *Issue:* > Idle logout wizard (with "logout now" and "stay logged in" is not shown) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[
https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3457:
-
Description:
1)
*Steps:*
1. Configured ranger.service.inactivity.timeout to 45 sec
2. Opened ranger UI on multiple tabs.
3. Left the session idle for 40 secs
4. once the popup for session idle going to expire shows up clicked on the
"stay logged in" button and performed an operation in one of the tabs.
*Observation*
# Other tabs which were opened removed the RangerSessionID, but the tab which
became active before timeout still using the same RangerSessionID.
# Clicking a link from the above active tab to a new tab still uses the same
RangerSessionID which was removed earlier
# But when clicking ranger ui from CP it opens with a new RangerSessionID
*Note:*
Though using RangerSessionID which was removed in other tabs, i was able to
navigate and perform policy updates. But not sure if any other action will fail
based on session which was removed
2)
*Steps:*
1. Configured ranger.service.inactivity.timeout to 40 sec and restarted Ranger
2. Open Ranger UI on an incognito window with hrt_qa/Password@123
3. Didnt perform any operation / mouse operation for 4 mins
*{color:#de350b}Issue:{color}*
Idle logout wizard (with "logout now" and "stay logged in" is not shown)
was:
*Steps:*
1. Configured ranger.service.inactivity.timeout to 45 sec
2. Opened ranger UI on multiple tabs.
3. Left the session idle for 40 secs
4. once the popup for session idle going to expire shows up clicked on the
"stay logged in" button and performed an operation in one of the tabs.
*Observation*
# Other tabs which were opened removed the RangerSessionID, but the tab which
became active before timeout still using the same RangerSessionID.
# Clicking a link from the above active tab to a new tab still uses the same
RangerSessionID which was removed earlier
# But when clicking ranger ui from CP it opens with a new RangerSessionID
*Note:*
Though using RangerSessionID which was removed in other tabs, i was able to
navigate and perform policy updates. But not sure if any other action will fail
based on session which was removed
> [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle
> timeout other active tab still continues with old/invalid session cookie.
> ---
>
> Key: RANGER-3457
> URL: https://issues.apache.org/jira/browse/RANGER-3457
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Nitin Galave
>Assignee: Nitin Galave
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 0002-RANGER-3457.patch
>
>
> 1)
> *Steps:*
> 1. Configured ranger.service.inactivity.timeout to 45 sec
> 2. Opened ranger UI on multiple tabs.
> 3. Left the session idle for 40 secs
> 4. once the popup for session idle going to expire shows up clicked on the
> "stay logged in" button and performed an operation in one of the tabs.
> *Observation*
> # Other tabs which were opened removed the RangerSessionID, but the tab
> which became active before timeout still using the same RangerSessionID.
> # Clicking a link from the above active tab to a new tab still uses the same
> RangerSessionID which was removed earlier
> # But when clicking ranger ui from CP it opens with a new RangerSessionID
> *Note:*
> Though using RangerSessionID which was removed in other tabs, i was able to
> navigate and perform policy updates. But not sure if any other action will
> fail based on session which was removed
> 2)
> *Steps:*
> 1. Configured ranger.service.inactivity.timeout to 40 sec and restarted
> Ranger
> 2. Open Ranger UI on an incognito window with hrt_qa/Password@123
> 3. Didnt perform any operation / mouse operation for 4 mins
> *{color:#de350b}Issue:{color}*
> Idle logout wizard (with "logout now" and "stay logged in" is not shown)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[
https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3457:
-
Description:
1)
*Steps:*
1. Configured ranger.service.inactivity.timeout to 45 sec
2. Opened ranger UI on multiple tabs.
3. Left the session idle for 40 secs
4. once the popup for session idle going to expire shows up clicked on the
"stay logged in" button and performed an operation in one of the tabs.
*Observation*
# Other tabs which were opened removed the RangerSessionID, but the tab which
became active before timeout still using the same RangerSessionID.
# Clicking a link from the above active tab to a new tab still uses the same
RangerSessionID which was removed earlier
# But when clicking ranger ui from CP it opens with a new RangerSessionID
*Note:*
Though using RangerSessionID which was removed in other tabs, i was able to
navigate and perform policy updates. But not sure if any other action will fail
based on session which was removed
2)
*Steps:*
1. Configured ranger.service.inactivity.timeout to 40 sec and restarted Ranger
2. Open Ranger UI on an incognito window with hrt_qa/Password@123
3. Didnt perform any operation / mouse operation for 4 mins
*Issue:*
Idle logout wizard (with "logout now" and "stay logged in" is not shown)
was:
1)
*Steps:*
1. Configured ranger.service.inactivity.timeout to 45 sec
2. Opened ranger UI on multiple tabs.
3. Left the session idle for 40 secs
4. once the popup for session idle going to expire shows up clicked on the
"stay logged in" button and performed an operation in one of the tabs.
*Observation*
# Other tabs which were opened removed the RangerSessionID, but the tab which
became active before timeout still using the same RangerSessionID.
# Clicking a link from the above active tab to a new tab still uses the same
RangerSessionID which was removed earlier
# But when clicking ranger ui from CP it opens with a new RangerSessionID
*Note:*
Though using RangerSessionID which was removed in other tabs, i was able to
navigate and perform policy updates. But not sure if any other action will fail
based on session which was removed
2)
*Steps:*
1. Configured ranger.service.inactivity.timeout to 40 sec and restarted Ranger
2. Open Ranger UI on an incognito window with hrt_qa/Password@123
3. Didnt perform any operation / mouse operation for 4 mins
*{color:#de350b}Issue:{color}*
Idle logout wizard (with "logout now" and "stay logged in" is not shown)
> [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle
> timeout other active tab still continues with old/invalid session cookie.
> ---
>
> Key: RANGER-3457
> URL: https://issues.apache.org/jira/browse/RANGER-3457
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Nitin Galave
>Assignee: Nitin Galave
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 0002-RANGER-3457.patch
>
>
> 1)
> *Steps:*
> 1. Configured ranger.service.inactivity.timeout to 45 sec
> 2. Opened ranger UI on multiple tabs.
> 3. Left the session idle for 40 secs
> 4. once the popup for session idle going to expire shows up clicked on the
> "stay logged in" button and performed an operation in one of the tabs.
> *Observation*
> # Other tabs which were opened removed the RangerSessionID, but the tab
> which became active before timeout still using the same RangerSessionID.
> # Clicking a link from the above active tab to a new tab still uses the same
> RangerSessionID which was removed earlier
> # But when clicking ranger ui from CP it opens with a new RangerSessionID
> *Note:*
> Though using RangerSessionID which was removed in other tabs, i was able to
> navigate and perform policy updates. But not sure if any other action will
> fail based on session which was removed
> 2)
> *Steps:*
> 1. Configured ranger.service.inactivity.timeout to 40 sec and restarted
> Ranger
> 2. Open Ranger UI on an incognito window with hrt_qa/Password@123
> 3. Didnt perform any operation / mouse operation for 4 mins
> *Issue:*
> Idle logout wizard (with "logout now" and "stay logged in" is not shown)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-3455) [Logout-Ranger] Should either be disabled/ should redirect to knox logout page
[ https://issues.apache.org/jira/browse/RANGER-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422149#comment-17422149 ] Nitin Galave commented on RANGER-3455: -- Committed to apache [master| https://github.com/apache/ranger/commit/c33ff07b689397520d874cde377c1853b9830278] and [ranger-2.2|https://github.com/apache/ranger/commit/e192fd1eeeb43ddf9bb3e027e52bac146ddfcb94] branch. > [Logout-Ranger] Should either be disabled/ should redirect to knox logout page > -- > > Key: RANGER-3455 > URL: https://issues.apache.org/jira/browse/RANGER-3455 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3455.patch, image-2021-09-23-21-30-04-791.png > > > *Steps:* > 1. Click on Ranger UI from CP > 2. Click on logout button from ranger home page. > *Observation:* > For now we see that it lands on below page. But it would be better if we > disable logout button /land on knox logout page . > !image-2021-09-23-21-30-04-791.png|width=322,height=132! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3457: - Attachment: 0002-RANGER-3457.patch > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0002-RANGER-3457.patch > > > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3457: - Attachment: (was: 0001-RANGER-3457.patch) > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0002-RANGER-3457.patch > > > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
[ https://issues.apache.org/jira/browse/RANGER-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3457: - Attachment: 0001-RANGER-3457.patch > [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle > timeout other active tab still continues with old/invalid session cookie. > --- > > Key: RANGER-3457 > URL: https://issues.apache.org/jira/browse/RANGER-3457 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3457.patch > > > *Steps:* > 1. Configured ranger.service.inactivity.timeout to 45 sec > 2. Opened ranger UI on multiple tabs. > 3. Left the session idle for 40 secs > 4. once the popup for session idle going to expire shows up clicked on the > "stay logged in" button and performed an operation in one of the tabs. > *Observation* > # Other tabs which were opened removed the RangerSessionID, but the tab > which became active before timeout still using the same RangerSessionID. > # Clicking a link from the above active tab to a new tab still uses the same > RangerSessionID which was removed earlier > # But when clicking ranger ui from CP it opens with a new RangerSessionID > *Note:* > Though using RangerSessionID which was removed in other tabs, i was able to > navigate and perform policy updates. But not sure if any other action will > fail based on session which was removed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3457) [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie.
Nitin Galave created RANGER-3457: Summary: [Session Timeout-Ranger]With multiple tabs if one tab encounters session idle timeout other active tab still continues with old/invalid session cookie. Key: RANGER-3457 URL: https://issues.apache.org/jira/browse/RANGER-3457 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave *Steps:* 1. Configured ranger.service.inactivity.timeout to 45 sec 2. Opened ranger UI on multiple tabs. 3. Left the session idle for 40 secs 4. once the popup for session idle going to expire shows up clicked on the "stay logged in" button and performed an operation in one of the tabs. *Observation* # Other tabs which were opened removed the RangerSessionID, but the tab which became active before timeout still using the same RangerSessionID. # Clicking a link from the above active tab to a new tab still uses the same RangerSessionID which was removed earlier # But when clicking ranger ui from CP it opens with a new RangerSessionID *Note:* Though using RangerSessionID which was removed in other tabs, i was able to navigate and perform policy updates. But not sure if any other action will fail based on session which was removed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3455) [Logout-Ranger] Should either be disabled/ should redirect to knox logout page
[ https://issues.apache.org/jira/browse/RANGER-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3455: - Attachment: 0001-RANGER-3455.patch > [Logout-Ranger] Should either be disabled/ should redirect to knox logout page > -- > > Key: RANGER-3455 > URL: https://issues.apache.org/jira/browse/RANGER-3455 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3455.patch, image-2021-09-23-21-30-04-791.png > > > *Steps:* > 1. Click on Ranger UI from CP > 2. Click on logout button from ranger home page. > *Observation:* > For now we see that it lands on below page. But it would be better if we > disable logout button /land on knox logout page . > !image-2021-09-23-21-30-04-791.png|width=322,height=132! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3455) [Logout-Ranger] Should either be disabled/ should redirect to knox logout page
[ https://issues.apache.org/jira/browse/RANGER-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3455: - Description: *Steps:* 1. Click on Ranger UI from CP 2. Click on logout button from ranger home page. *Observation:* For now we see that it lands on below page. But it would be better if we disable logout button /land on knox logout page . !image-2021-09-23-21-30-04-791.png|width=322,height=132! was: *Steps:* 1. Click on Ranger UI from CP 2. Click on logout button from ranger home page. *Observation:* For now we see that it lands on below page. But it would be better if we disable logout button /land on knox logout page . !image-2021-09-23-21-30-04-791.png! > [Logout-Ranger] Should either be disabled/ should redirect to knox logout page > -- > > Key: RANGER-3455 > URL: https://issues.apache.org/jira/browse/RANGER-3455 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: image-2021-09-23-21-30-04-791.png > > > *Steps:* > 1. Click on Ranger UI from CP > 2. Click on logout button from ranger home page. > *Observation:* > For now we see that it lands on below page. But it would be better if we > disable logout button /land on knox logout page . > !image-2021-09-23-21-30-04-791.png|width=322,height=132! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3455) [Logout-Ranger] Should either be disabled/ should redirect to knox logout page
[ https://issues.apache.org/jira/browse/RANGER-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3455: - Attachment: image-2021-09-23-21-30-04-791.png > [Logout-Ranger] Should either be disabled/ should redirect to knox logout page > -- > > Key: RANGER-3455 > URL: https://issues.apache.org/jira/browse/RANGER-3455 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: image-2021-09-23-21-30-04-791.png > > > *Steps:* > 1. Click on Ranger UI from CP > 2. Click on logout button from ranger home page. > *Observation:* > For now we see that it lands on below page. But it would be better if we > disable logout button /land on knox logout page . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3455) [Logout-Ranger] Should either be disabled/ should redirect to knox logout page
[ https://issues.apache.org/jira/browse/RANGER-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3455: - Description: *Steps:* 1. Click on Ranger UI from CP 2. Click on logout button from ranger home page. *Observation:* For now we see that it lands on below page. But it would be better if we disable logout button /land on knox logout page . !image-2021-09-23-21-30-04-791.png! was: *Steps:* 1. Click on Ranger UI from CP 2. Click on logout button from ranger home page. *Observation:* For now we see that it lands on below page. But it would be better if we disable logout button /land on knox logout page . > [Logout-Ranger] Should either be disabled/ should redirect to knox logout page > -- > > Key: RANGER-3455 > URL: https://issues.apache.org/jira/browse/RANGER-3455 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: image-2021-09-23-21-30-04-791.png > > > *Steps:* > 1. Click on Ranger UI from CP > 2. Click on logout button from ranger home page. > *Observation:* > For now we see that it lands on below page. But it would be better if we > disable logout button /land on knox logout page . > !image-2021-09-23-21-30-04-791.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3455) [Logout-Ranger] Should either be disabled/ should redirect to knox logout page
Nitin Galave created RANGER-3455: Summary: [Logout-Ranger] Should either be disabled/ should redirect to knox logout page Key: RANGER-3455 URL: https://issues.apache.org/jira/browse/RANGER-3455 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave *Steps:* 1. Click on Ranger UI from CP 2. Click on logout button from ranger home page. *Observation:* For now we see that it lands on below page. But it would be better if we disable logout button /land on knox logout page . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3443) "X-Permitted-Cross-Domain-Policies" header not set by Ranger UI
Nitin Galave created RANGER-3443:
Summary: "X-Permitted-Cross-Domain-Policies" header not set by
Ranger UI
Key: RANGER-3443
URL: https://issues.apache.org/jira/browse/RANGER-3443
Project: Ranger
Issue Type: Improvement
Components: Ranger
Reporter: Nitin Galave
Assignee: Nitin Galave
Ranger does not return "X-Permitted-Cross-Domain-Policies" response header.
OWASP best practices suggest explicitly setting this header to "none":
{code:java}
X-Permitted-Cross-Domain-Policies: none{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3388) Session Inactivity Timeout: Ranger UI part.
[ https://issues.apache.org/jira/browse/RANGER-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3388: - Fix Version/s: 2.2.0 > Session Inactivity Timeout: Ranger UI part. > --- > > Key: RANGER-3388 > URL: https://issues.apache.org/jira/browse/RANGER-3388 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 2.2.0 > > Attachments: 0001-RANGER-3388.patch > > > *Background* > Ranger users who log in via one of the supported authentication flavors stay > logged in until they choose to log out. > This is a security hole in the scenario where the user has logged in and has > left their desk. The inactivity does not result in early log out. > This implementation addresses that problem. > *Scenarios* > * Login to single session. > * Login to multiple tabs. > * Login to multiple services each having its own inactivity detection and > logout implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3388) Session Inactivity Timeout: Ranger UI part.
[ https://issues.apache.org/jira/browse/RANGER-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417652#comment-17417652 ] Nitin Galave commented on RANGER-3388: -- Committed to apache [master|https://github.com/apache/ranger/commit/321435f45ee6ea2090c5339d1eda6ed5b11693a1] branch. Committed to [ranger-2.2|https://github.com/apache/ranger/commit/afb4d982cdcf4203db046f556a829ded75151c5c] branch. > Session Inactivity Timeout: Ranger UI part. > --- > > Key: RANGER-3388 > URL: https://issues.apache.org/jira/browse/RANGER-3388 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3388.patch > > > *Background* > Ranger users who log in via one of the supported authentication flavors stay > logged in until they choose to log out. > This is a security hole in the scenario where the user has logged in and has > left their desk. The inactivity does not result in early log out. > This implementation addresses that problem. > *Scenarios* > * Login to single session. > * Login to multiple tabs. > * Login to multiple services each having its own inactivity detection and > logout implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3293) Show user source details on user tab in ranger UI.
[ https://issues.apache.org/jira/browse/RANGER-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411936#comment-17411936 ] Nitin Galave commented on RANGER-3293: -- Committed to [Apache-master|https://github.com/apache/ranger/commit/fcfed2062b0028b758893d898ec430ed4ea62328] branch. Committed to [ranger-2.2|https://github.com/apache/ranger/commit/79f21e1de687e5bbf7b24f2695033c7f0825775f] branch. > Show user source details on user tab in ranger UI. > -- > > Key: RANGER-3293 > URL: https://issues.apache.org/jira/browse/RANGER-3293 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3293.patch, 0002-RANGER-3293.patch > > > Two new attributes are added when users are synced. > Show them to the User details page Ranger UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3362) UI Improvements.
[ https://issues.apache.org/jira/browse/RANGER-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407085#comment-17407085 ] Nitin Galave commented on RANGER-3362: -- Committed to [Apache master|https://github.com/apache/ranger/commit/dfc018b410ed643a94ad2218c831043bd2195f55] branch. Committed to [ranger-2.2|https://github.com/apache/ranger/commit/7dc0950191203253d8a598283a15b91ab2c4660a] branch. > UI Improvements. > > > Key: RANGER-3362 > URL: https://issues.apache.org/jira/browse/RANGER-3362 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3362.patch > > > Issue 1: Even the checkbox is selected still during deletion of role > prompting pop up saying " Select the role first". > Steps: > 1.Create policy and associate any role to it. > 2.Try to delete that role - select the role and click on delete icon- > 3.Again try to delete the same role and observe- It will ask to select a role > again but role is already selected > Actual Result: > > Issue 2: Not able to save the policy when I removed the role / group and > permissions during updating. > Steps: > 1.Create a policy and associate the role/group to it and save the policy. > 2.Remove the role/group + permissions from the same policy ,click on save > and observe. > Actual Result: Getting error message saying "error code[3020], reason[All of > users, user-groups and roles collections on the policy item were null/empty]". > Expected Result: User should able to update the policy successfully. > Improvement 3: When any role is associated with the particular user and group > and the customer is trying to delete that user and group then a proper > validation message is required. > Steps: > 1.Create a role and associate any user and group to it. > 2.Try to delete that user and group and observe. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3388) Session Inactivity Timeout: Ranger UI part.
[ https://issues.apache.org/jira/browse/RANGER-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3388: - Attachment: 0001-RANGER-3388.patch > Session Inactivity Timeout: Ranger UI part. > --- > > Key: RANGER-3388 > URL: https://issues.apache.org/jira/browse/RANGER-3388 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3388.patch > > > *Background* > Ranger users who log in via one of the supported authentication flavors stay > logged in until they choose to log out. > This is a security hole in the scenario where the user has logged in and has > left their desk. The inactivity does not result in early log out. > This implementation addresses that problem. > *Scenarios* > * Login to single session. > * Login to multiple tabs. > * Login to multiple services each having its own inactivity detection and > logout implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3388) Session Inactivity Timeout: Ranger UI part.
Nitin Galave created RANGER-3388: Summary: Session Inactivity Timeout: Ranger UI part. Key: RANGER-3388 URL: https://issues.apache.org/jira/browse/RANGER-3388 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave *Background* Ranger users who log in via one of the supported authentication flavors stay logged in until they choose to log out. This is a security hole in the scenario where the user has logged in and has left their desk. The inactivity does not result in early log out. This implementation addresses that problem. *Scenarios* * Login to single session. * Login to multiple tabs. * Login to multiple services each having its own inactivity detection and logout implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3336) All policies are exported, when searching reports using roles
[ https://issues.apache.org/jira/browse/RANGER-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3336: - Fix Version/s: 2.2.0 > All policies are exported, when searching reports using roles > - > > Key: RANGER-3336 > URL: https://issues.apache.org/jira/browse/RANGER-3336 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 2.2.0 > > Attachments: 0001-RANGER-3336.patch > > > On the Reports page, when policies are searched using Role name, > and then exported, all the policies are listed in the downloaded file even if > only > one policy is shown in the search result. > Steps to reproduce : > 1. Create a policy on any role > 2. On the Reports page, search for policies using only the role name. > 3. Export the policies. > 4. In the downloaded file, all policies available in Ranger will be listed > even if the search results had one or two policies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3336) All policies are exported, when searching reports using roles
[ https://issues.apache.org/jira/browse/RANGER-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402189#comment-17402189 ] Nitin Galave commented on RANGER-3336: -- Committed to [Apache-master|https://github.com/apache/ranger/commit/284e1f0e47530bbff9dee9289f33950680d13403] branch. Committed to [ranger-2.2|https://github.com/apache/ranger/commit/284e1f0e47530bbff9dee9289f33950680d13403] branch. > All policies are exported, when searching reports using roles > - > > Key: RANGER-3336 > URL: https://issues.apache.org/jira/browse/RANGER-3336 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3336.patch > > > On the Reports page, when policies are searched using Role name, > and then exported, all the policies are listed in the downloaded file even if > only > one policy is shown in the search result. > Steps to reproduce : > 1. Create a policy on any role > 2. On the Reports page, search for policies using only the role name. > 3. Export the policies. > 4. In the downloaded file, all policies available in Ranger will be listed > even if the search results had one or two policies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3052) Can not search by object name in page /reports/audit/admin
[ https://issues.apache.org/jira/browse/RANGER-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401046#comment-17401046 ] Nitin Galave commented on RANGER-3052: -- HI [~fengxianjing], Build is failing with your patch (There are test failures). Can you please update the patch? Thanks Nitin > Can not search by object name in page /reports/audit/admin > -- > > Key: RANGER-3052 > URL: https://issues.apache.org/jira/browse/RANGER-3052 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: fengxianjing >Assignee: fengxianjing >Priority: Major > Attachments: > 0001-RANGER-3052-support-search-by-object-name-in-admin-a.patch > > > We have thousands operation per day, and we usually search by policy name for > find out who modified a specified policy. At present, we can only query the > database -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3293) Show user source details on user tab in ranger UI.
[ https://issues.apache.org/jira/browse/RANGER-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3293: - Attachment: 0002-RANGER-3293.patch > Show user source details on user tab in ranger UI. > -- > > Key: RANGER-3293 > URL: https://issues.apache.org/jira/browse/RANGER-3293 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3293.patch, 0002-RANGER-3293.patch > > > Two new attributes are added when users are synced. > Show them to the User details page Ranger UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3362) UI Improvements.
[ https://issues.apache.org/jira/browse/RANGER-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3362: - Attachment: 0001-RANGER-3362.patch > UI Improvements. > > > Key: RANGER-3362 > URL: https://issues.apache.org/jira/browse/RANGER-3362 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3362.patch > > > Issue 1: Even the checkbox is selected still during deletion of role > prompting pop up saying " Select the role first". > Steps: > 1.Create policy and associate any role to it. > 2.Try to delete that role - select the role and click on delete icon- > 3.Again try to delete the same role and observe- It will ask to select a role > again but role is already selected > Actual Result: > > Issue 2: Not able to save the policy when I removed the role / group and > permissions during updating. > Steps: > 1.Create a policy and associate the role/group to it and save the policy. > 2.Remove the role/group + permissions from the same policy ,click on save > and observe. > Actual Result: Getting error message saying "error code[3020], reason[All of > users, user-groups and roles collections on the policy item were null/empty]". > Expected Result: User should able to update the policy successfully. > Improvement 3: When any role is associated with the particular user and group > and the customer is trying to delete that user and group then a proper > validation message is required. > Steps: > 1.Create a role and associate any user and group to it. > 2.Try to delete that user and group and observe. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3362) UI Improvements.
Nitin Galave created RANGER-3362: Summary: UI Improvements. Key: RANGER-3362 URL: https://issues.apache.org/jira/browse/RANGER-3362 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave Issue 1: Even the checkbox is selected still during deletion of role prompting pop up saying " Select the role first". Steps: 1.Create policy and associate any role to it. 2.Try to delete that role - select the role and click on delete icon- 3.Again try to delete the same role and observe- It will ask to select a role again but role is already selected Actual Result: Issue 2: Not able to save the policy when I removed the role / group and permissions during updating. Steps: 1.Create a policy and associate the role/group to it and save the policy. 2.Remove the role/group + permissions from the same policy ,click on save and observe. Actual Result: Getting error message saying "error code[3020], reason[All of users, user-groups and roles collections on the policy item were null/empty]". Expected Result: User should able to update the policy successfully. Improvement 3: When any role is associated with the particular user and group and the customer is trying to delete that user and group then a proper validation message is required. Steps: 1.Create a role and associate any user and group to it. 2.Try to delete that user and group and observe. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3338) Masking and Row filter policy are getting exported from report page when Policy type=Access
[ https://issues.apache.org/jira/browse/RANGER-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3338: - Fix Version/s: 2.2.0 > Masking and Row filter policy are getting exported from report page when > Policy type=Access > --- > > Key: RANGER-3338 > URL: https://issues.apache.org/jira/browse/RANGER-3338 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Nitin Galave >Priority: Major > Fix For: 2.2.0 > > Attachments: 0001-RANGER-3338.patch > > > Steps > 1.Create a policy in hive masking and hive row. > 2.Go to report page > 3.Export excel, csv and json > 4.Check the exported file it has masking and row filter policy also. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3338) Masking and Row filter policy are getting exported from report page when Policy type=Access
[ https://issues.apache.org/jira/browse/RANGER-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382019#comment-17382019 ] Nitin Galave commented on RANGER-3338: -- Committed to [Apache-master|https://github.com/apache/ranger/commit/a2d4360f581ae90d190e73b8947f4db9db132eea] branch. Committed to [ranger-2.2|https://github.com/apache/ranger/commit/6bf1ff25e6964d34d7bfdf0224e96624d7dbfc14] branch. > Masking and Row filter policy are getting exported from report page when > Policy type=Access > --- > > Key: RANGER-3338 > URL: https://issues.apache.org/jira/browse/RANGER-3338 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3338.patch > > > Steps > 1.Create a policy in hive masking and hive row. > 2.Go to report page > 3.Export excel, csv and json > 4.Check the exported file it has masking and row filter policy also. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-3338) Masking and Row filter policy are getting exported from report page when Policy type=Access
[ https://issues.apache.org/jira/browse/RANGER-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave reassigned RANGER-3338: Assignee: Nitin Galave > Masking and Row filter policy are getting exported from report page when > Policy type=Access > --- > > Key: RANGER-3338 > URL: https://issues.apache.org/jira/browse/RANGER-3338 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3338.patch > > > Steps > 1.Create a policy in hive masking and hive row. > 2.Go to report page > 3.Export excel, csv and json > 4.Check the exported file it has masking and row filter policy also. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3338) Masking and Row filter policy are getting exported from report page when Policy type=Access
[ https://issues.apache.org/jira/browse/RANGER-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3338: - Attachment: 0001-RANGER-3338.patch > Masking and Row filter policy are getting exported from report page when > Policy type=Access > --- > > Key: RANGER-3338 > URL: https://issues.apache.org/jira/browse/RANGER-3338 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Priority: Major > Attachments: 0001-RANGER-3338.patch > > > Steps > 1.Create a policy in hive masking and hive row. > 2.Go to report page > 3.Export excel, csv and json > 4.Check the exported file it has masking and row filter policy also. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3336) All policies are exported, when searching reports using roles
[ https://issues.apache.org/jira/browse/RANGER-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3336: - Attachment: 0001-RANGER-3336.patch > All policies are exported, when searching reports using roles > - > > Key: RANGER-3336 > URL: https://issues.apache.org/jira/browse/RANGER-3336 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3336.patch > > > On the Reports page, when policies are searched using Role name, > and then exported, all the policies are listed in the downloaded file even if > only > one policy is shown in the search result. > Steps to reproduce : > 1. Create a policy on any role > 2. On the Reports page, search for policies using only the role name. > 3. Export the policies. > 4. In the downloaded file, all policies available in Ranger will be listed > even if the search results had one or two policies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3336) All policies are exported, when searching reports using roles
Nitin Galave created RANGER-3336: Summary: All policies are exported, when searching reports using roles Key: RANGER-3336 URL: https://issues.apache.org/jira/browse/RANGER-3336 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave On the Reports page, when policies are searched using Role name, and then exported, all the policies are listed in the downloaded file even if only one policy is shown in the search result. Steps to reproduce : 1. Create a policy on any role 2. On the Reports page, search for policies using only the role name. 3. Export the policies. 4. In the downloaded file, all policies available in Ranger will be listed even if the search results had one or two policies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3327) List of services in "Security Zones" is not full
[ https://issues.apache.org/jira/browse/RANGER-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376758#comment-17376758 ] Nitin Galave commented on RANGER-3327: -- Hi [~fullhouse], We allow only the first 100 services in the security zone Select Resources services field in the older ranger version. This was updated to 200 in [RANGER-2762|https://issues.apache.org/jira/browse/RANGER-2767]. Thanks, Nitin > List of services in "Security Zones" is not full > > > Key: RANGER-3327 > URL: https://issues.apache.org/jira/browse/RANGER-3327 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.0.0, 2.1.0, 3.0.0, 2.2.0 >Reporter: Konstantin Tsypin >Priority: Major > Attachments: image-2021-07-07-17-49-59-777.png, > image-2021-07-07-17-49-59-815.png, image-2021-07-07-17-50-20-612.png, > image-2021-07-07-17-50-39-688.png, image-2021-07-07-17-50-39-729.png > > > Hi there. We have about N hundreds services on Apache Ranger main page. > So in security zones we didnot see all services, it's snap of some first > added. > Look at the screenshots. Seemed like problem with pagelisting or something > like that. > 1) Services: > !image-2021-07-07-17-40-13-671.png! > 2) Security zones performance: > !image-2021-07-07-17-41-52-133.png! > The tag choice does not change any (look screens on task comment) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3323) Ranger Hive Table lookup is not working.
[
https://issues.apache.org/jira/browse/RANGER-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370579#comment-17370579
]
Nitin Galave commented on RANGER-3323:
--
Committed to Apache
[master|https://github.com/apache/ranger/commit/3db20090ba448f844eee69661e11f008ca259128]
branch.
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/9651c029e95bf09bb7054308fee1abb1a236d49f]
branch.
> Ranger Hive Table lookup is not working.
>
>
> Key: RANGER-3323
> URL: https://issues.apache.org/jira/browse/RANGER-3323
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Nitin Galave
>Assignee: Nitin Galave
>Priority: Major
> Attachments: 0001-RANGER-3323.patch
>
>
> Ranger Hive table lookup is failing with the below error message.
> {code:java}
> 2021-06-23 09:13:36,206 INFO
> org.apache.hadoop.hive.metastore.thrift.TCustomSocket: [main]: Buffer size
> for TSocket is: 8192
> 2021-06-23 09:13:36,211 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
> [pool-10-thread-74]: 51: get_multi_table : db={ tbls=null
> 2021-06-23 09:13:36,211 INFO
> org.apache.hadoop.hive.metastore.HiveMetaStore.audit: [pool-10-thread-74]:
> ugi=rangerlookup/mmrngrhive-1.mmrngrhive.root.hwx.s...@root.hwx.site
> ip=172.27.28.139cmd=get_multi_table : db={ tbls=null
> 2021-06-23 09:13:36,212 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
> [pool-10-thread-74]: 51: Opening raw store with implementation
> class:org.apache.hadoop.hive.metastore.ObjectStore
> 2021-06-23 09:13:36,213 INFO org.apache.hadoop.hive.metastore.ObjectStore:
> [pool-10-thread-74]: RawStore:
> org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with
> PersistenceManager: null will be shutdown
> 2021-06-23 09:13:36,214 INFO org.apache.hadoop.hive.metastore.ObjectStore:
> [pool-10-thread-74]: RawStore:
> org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with
> PersistenceManager: org.datanucleus.api.jdo.JDOPersistenceManager@60bbf86c
> created in the thread with id: 292
> 2021-06-23 09:13:36,216 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
> [pool-10-thread-74]: Created RawStore:
> org.apache.hadoop.hive.metastore.ObjectStore@619f1981 from thread id: 292
> 2021-06-23 09:13:36,219 WARN org.apache.hadoop.hive.metastore.ObjectStore:
> [pool-10-thread-74]: Failed to get database hive.{, returning
> NoSuchObjectException
> 2021-06-23 09:13:36,219 ERROR
> org.apache.hadoop.hive.metastore.RetryingHMSHandler: [pool-10-thread-74]:
> UnknownDBException(message:Could not find database hive.{: {)
> at
> org.apache.hadoop.hive.metastore.ObjectStore.getTableObjectsByName(ObjectStore.java:2255)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:97)
> at com.sun.proxy.$Proxy32.getTableObjectsByName(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.getTableObjectsInternal(HiveMetaStore.java:3773)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_table_objects_by_name_req(HiveMetaStore.java:3740)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:160)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:121)
> at com.sun.proxy.$Proxy41.get_table_objects_by_name_req(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18454)
> at
> org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18438)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:643)
> at
> org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:638)
> at
[jira] [Updated] (RANGER-3323) Ranger Hive Table lookup is not working.
[
https://issues.apache.org/jira/browse/RANGER-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3323:
-
Description:
Ranger Hive table lookup is failing with the below error message.
{code:java}
2021-06-23 09:13:36,206 INFO
org.apache.hadoop.hive.metastore.thrift.TCustomSocket: [main]: Buffer size for
TSocket is: 8192
2021-06-23 09:13:36,211 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: 51: get_multi_table : db={ tbls=null
2021-06-23 09:13:36,211 INFO
org.apache.hadoop.hive.metastore.HiveMetaStore.audit: [pool-10-thread-74]:
ugi=rangerlookup/mmrngrhive-1.mmrngrhive.root.hwx.s...@root.hwx.site
ip=172.27.28.139cmd=get_multi_table : db={ tbls=null
2021-06-23 09:13:36,212 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: 51: Opening raw store with implementation
class:org.apache.hadoop.hive.metastore.ObjectStore
2021-06-23 09:13:36,213 INFO org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with PersistenceManager:
null will be shutdown
2021-06-23 09:13:36,214 INFO org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with PersistenceManager:
org.datanucleus.api.jdo.JDOPersistenceManager@60bbf86c created in the thread
with id: 292
2021-06-23 09:13:36,216 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: Created RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981 from thread id: 292
2021-06-23 09:13:36,219 WARN org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: Failed to get database hive.{, returning
NoSuchObjectException
2021-06-23 09:13:36,219 ERROR
org.apache.hadoop.hive.metastore.RetryingHMSHandler: [pool-10-thread-74]:
UnknownDBException(message:Could not find database hive.{: {)
at
org.apache.hadoop.hive.metastore.ObjectStore.getTableObjectsByName(ObjectStore.java:2255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:97)
at com.sun.proxy.$Proxy32.getTableObjectsByName(Unknown Source)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.getTableObjectsInternal(HiveMetaStore.java:3773)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_table_objects_by_name_req(HiveMetaStore.java:3740)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:160)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:121)
at com.sun.proxy.$Proxy41.get_table_objects_by_name_req(Unknown Source)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18454)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18438)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:643)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:638)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1898)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:638)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2021-06-23 09:13:37,139 INFO org.apache.hadoop.hive.ql.txn.compactor.Cleaner:
[Thread-14]:
[jira] [Updated] (RANGER-3323) Ranger Hive Table lookup is not working.
[
https://issues.apache.org/jira/browse/RANGER-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3323:
-
Description:
Ranger Hive table lookup is failing with below error massage.
{code:java}
2021-06-23 09:13:36,206 INFO
org.apache.hadoop.hive.metastore.thrift.TCustomSocket: [main]: Buffer size for
TSocket is: 8192
2021-06-23 09:13:36,211 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: 51: get_multi_table : db={ tbls=null
2021-06-23 09:13:36,211 INFO
org.apache.hadoop.hive.metastore.HiveMetaStore.audit: [pool-10-thread-74]:
ugi=rangerlookup/mmrngrhive-1.mmrngrhive.root.hwx.s...@root.hwx.site
ip=172.27.28.139cmd=get_multi_table : db={ tbls=null
2021-06-23 09:13:36,212 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: 51: Opening raw store with implementation
class:org.apache.hadoop.hive.metastore.ObjectStore
2021-06-23 09:13:36,213 INFO org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with PersistenceManager:
null will be shutdown
2021-06-23 09:13:36,214 INFO org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with PersistenceManager:
org.datanucleus.api.jdo.JDOPersistenceManager@60bbf86c created in the thread
with id: 292
2021-06-23 09:13:36,216 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: Created RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981 from thread id: 292
2021-06-23 09:13:36,219 WARN org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: Failed to get database hive.{, returning
NoSuchObjectException
2021-06-23 09:13:36,219 ERROR
org.apache.hadoop.hive.metastore.RetryingHMSHandler: [pool-10-thread-74]:
UnknownDBException(message:Could not find database hive.{: {)
at
org.apache.hadoop.hive.metastore.ObjectStore.getTableObjectsByName(ObjectStore.java:2255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:97)
at com.sun.proxy.$Proxy32.getTableObjectsByName(Unknown Source)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.getTableObjectsInternal(HiveMetaStore.java:3773)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_table_objects_by_name_req(HiveMetaStore.java:3740)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:160)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:121)
at com.sun.proxy.$Proxy41.get_table_objects_by_name_req(Unknown Source)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18454)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18438)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:643)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:638)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1898)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:638)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2021-06-23 09:13:37,139 INFO org.apache.hadoop.hive.ql.txn.compactor.Cleaner:
[Thread-14]:
[jira] [Updated] (RANGER-3323) Ranger Hive Table lookup is not working.
[
https://issues.apache.org/jira/browse/RANGER-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3323:
-
Description:
Ranger Hive table lookup is failing.
{code:java}
2021-06-23 09:13:36,206 INFO
org.apache.hadoop.hive.metastore.thrift.TCustomSocket: [main]: Buffer size for
TSocket is: 8192
2021-06-23 09:13:36,211 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: 51: get_multi_table : db={ tbls=null
2021-06-23 09:13:36,211 INFO
org.apache.hadoop.hive.metastore.HiveMetaStore.audit: [pool-10-thread-74]:
ugi=rangerlookup/mmrngrhive-1.mmrngrhive.root.hwx.s...@root.hwx.site
ip=172.27.28.139cmd=get_multi_table : db={ tbls=null
2021-06-23 09:13:36,212 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: 51: Opening raw store with implementation
class:org.apache.hadoop.hive.metastore.ObjectStore
2021-06-23 09:13:36,213 INFO org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with PersistenceManager:
null will be shutdown
2021-06-23 09:13:36,214 INFO org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981, with PersistenceManager:
org.datanucleus.api.jdo.JDOPersistenceManager@60bbf86c created in the thread
with id: 292
2021-06-23 09:13:36,216 INFO org.apache.hadoop.hive.metastore.HiveMetaStore:
[pool-10-thread-74]: Created RawStore:
org.apache.hadoop.hive.metastore.ObjectStore@619f1981 from thread id: 292
2021-06-23 09:13:36,219 WARN org.apache.hadoop.hive.metastore.ObjectStore:
[pool-10-thread-74]: Failed to get database hive.{, returning
NoSuchObjectException
2021-06-23 09:13:36,219 ERROR
org.apache.hadoop.hive.metastore.RetryingHMSHandler: [pool-10-thread-74]:
UnknownDBException(message:Could not find database hive.{: {)
at
org.apache.hadoop.hive.metastore.ObjectStore.getTableObjectsByName(ObjectStore.java:2255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:97)
at com.sun.proxy.$Proxy32.getTableObjectsByName(Unknown Source)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.getTableObjectsInternal(HiveMetaStore.java:3773)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_table_objects_by_name_req(HiveMetaStore.java:3740)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:160)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:121)
at com.sun.proxy.$Proxy41.get_table_objects_by_name_req(Unknown Source)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18454)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_table_objects_by_name_req.getResult(ThriftHiveMetastore.java:18438)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:643)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:638)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1898)
at
org.apache.hadoop.hive.metastore.security.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:638)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2021-06-23 09:13:37,139 INFO org.apache.hadoop.hive.ql.txn.compactor.Cleaner:
[Thread-14]: Cleaning based on min open txn
[jira] [Updated] (RANGER-3323) Ranger Hive Table lookup is not working.
[ https://issues.apache.org/jira/browse/RANGER-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3323: - Attachment: 0001-RANGER-3323.patch > Ranger Hive Table lookup is not working. > > > Key: RANGER-3323 > URL: https://issues.apache.org/jira/browse/RANGER-3323 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3323.patch > > > Ranger Hive table lookup is failing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3323) Ranger Hive Table lookup is not working.
Nitin Galave created RANGER-3323: Summary: Ranger Hive Table lookup is not working. Key: RANGER-3323 URL: https://issues.apache.org/jira/browse/RANGER-3323 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave Ranger Hive table lookup is failing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3301) [UI] in admin audit log tables not formatted correctly for long string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359040#comment-17359040 ] Nitin Galave commented on RANGER-3301: -- Patch committed to [ranger-2.2|https://github.com/apache/ranger/commit/d8db40445dc3a1920468f0dc6231ca6f9deb4407] branch. > [UI] in admin audit log tables not formatted correctly for long string value > for resources. > --- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: 0002-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log tables not formatted correctly for long string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Summary: [UI] in admin audit log tables not formatted correctly for long string value for resources. (was: [UI] in admin audit log tables not formatted correctly for lone string value for resources.) > [UI] in admin audit log tables not formatted correctly for long string value > for resources. > --- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0002-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log tables not formatted correctly for lone string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Summary: [UI] in admin audit log tables not formatted correctly for lone string value for resources. (was: [UI] in admin audit log tebles not formated correctly for lone string value for resources.) > [UI] in admin audit log tables not formatted correctly for lone string value > for resources. > --- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0002-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3306) Allow comma in policy resource text field.
[ https://issues.apache.org/jira/browse/RANGER-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3306: - Attachment: 0002-RANGER-3306.patch > Allow comma in policy resource text field. > -- > > Key: RANGER-3306 > URL: https://issues.apache.org/jira/browse/RANGER-3306 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3306.patch, 0002-RANGER-3306.patch > > > At policy creation time, When the user enters a comma in the resource field. > it creates a separate tag. > it is good if we add a comma in between the string. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3306) Allow comma in policy resource text field.
[ https://issues.apache.org/jira/browse/RANGER-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3306: - Description: At policy creation time, When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between the string. was: When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between the string. > Allow comma in policy resource text field. > -- > > Key: RANGER-3306 > URL: https://issues.apache.org/jira/browse/RANGER-3306 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3306.patch > > > At policy creation time, When the user enters a comma in the resource field. > it creates a separate tag. > it is good if we add a comma in between the string. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3306) Allow comma in policy resource text field.
[ https://issues.apache.org/jira/browse/RANGER-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3306: - Attachment: 0001-RANGER-3306.patch > Allow comma in policy resource text field. > -- > > Key: RANGER-3306 > URL: https://issues.apache.org/jira/browse/RANGER-3306 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3306.patch > > > When the user enters a comma in the resource field. it creates a separate tag. > it is good if we add a comma in between the string. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3306) Allow comma in policy resource text field.
[ https://issues.apache.org/jira/browse/RANGER-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3306: - Description: When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between the string. was: When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between string > Allow comma in policy resource text field. > -- > > Key: RANGER-3306 > URL: https://issues.apache.org/jira/browse/RANGER-3306 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > > When the user enters a comma in the resource field. it creates a separate tag. > it is good if we add a comma in between the string. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3306) Allow comma in policy resource text field.
[ https://issues.apache.org/jira/browse/RANGER-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3306: - Description: When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between string was: When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between sting > Allow comma in policy resource text field. > -- > > Key: RANGER-3306 > URL: https://issues.apache.org/jira/browse/RANGER-3306 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > > When the user enters a comma in the resource field. it creates a separate tag. > it is good if we add a comma in between string -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3306) Allow comma in policy resource text field.
Nitin Galave created RANGER-3306: Summary: Allow comma in policy resource text field. Key: RANGER-3306 URL: https://issues.apache.org/jira/browse/RANGER-3306 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave When the user enters a comma in the resource field. it creates a separate tag. it is good if we add a comma in between sting -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log tebles not formated correctly for lone string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Attachment: 0002-RANGER-3301.patch > [UI] in admin audit log tebles not formated correctly for lone string value > for resources. > -- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0002-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log tebles not formated correctly for lone string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Attachment: (was: 0001-RANGER-3301.patch) > [UI] in admin audit log tebles not formated correctly for lone string value > for resources. > -- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0002-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Description: Step to reproduce 1) Create hdfs service policy with resource path value to long string. 2)Check policy created to log on Audit => Admin tab 3)In policy details popup table not formatted correctly. was:There is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log tebles not formated correctly for lone string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Summary: [UI] in admin audit log tebles not formated correctly for lone string value for resources. (was: [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.) > [UI] in admin audit log tebles not formated correctly for lone string value > for resources. > -- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log tebles not formated correctly for lone string value for resources.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Attachment: (was: Screen Shot 2021-05-25 at 3.10.46 AM.png) > [UI] in admin audit log tebles not formated correctly for lone string value > for resources. > -- > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3301.patch > > > Step to reproduce > 1) Create hdfs service policy with resource path value to long string. > 2)Check policy created to log on Audit => Admin tab > 3)In policy details popup table not formatted correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Attachment: 0001-RANGER-3301.patch > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3301.patch, Screen Shot 2021-05-25 at > 3.10.46 AM.png > > > There is ranger policy with a big storage url , and in admin audit policy > detail table, fields are not correctly formatted, which gives impression that > storage-url exclude is set to > qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Description: There is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name (was: !Screen Shot 2021-05-25 at 3.10.46 AM.png! there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name) > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: Screen Shot 2021-05-25 at 3.10.46 AM.png > > > There is ranger policy with a big storage url , and in admin audit policy > detail table, fields are not correctly formatted, which gives impression that > storage-url exclude is set to > qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Attachment: Screen Shot 2021-05-25 at 3.10.46 AM.png > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: Screen Shot 2021-05-25 at 3.10.46 AM.png > > > there is ranger policy with a big storage url , and in admin audit policy > detail table, fields are not correctly formatted, which gives impression that > storage-url exclude is set to > qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Description: !Screen Shot 2021-05-25 at 3.10.46 AM.png! there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name (was: there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name) > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: Screen Shot 2021-05-25 at 3.10.46 AM.png > > > !Screen Shot 2021-05-25 at 3.10.46 AM.png! there is ranger policy with a big > storage url , and in admin audit policy detail table, fields are not > correctly formatted, which gives impression that storage-url exclude is set > to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
Nitin Galave created RANGER-3301: Summary: [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big. Key: RANGER-3301 URL: https://issues.apache.org/jira/browse/RANGER-3301 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3293) Show user source details on user tab in ranger UI.
[ https://issues.apache.org/jira/browse/RANGER-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3293: - Attachment: 0001-RANGER-3293.patch > Show user source details on user tab in ranger UI. > -- > > Key: RANGER-3293 > URL: https://issues.apache.org/jira/browse/RANGER-3293 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-3293.patch > > > Two new attributes are added when users are synced. > Show them to the User details page Ranger UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3293) Show user source details on user tab in ranger UI.
Nitin Galave created RANGER-3293: Summary: Show user source details on user tab in ranger UI. Key: RANGER-3293 URL: https://issues.apache.org/jira/browse/RANGER-3293 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave Two new attributes are added when users are synced. Show them to the User details page Ranger UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3269) [Ranger Audits UI] Long policy names get overlapped with enabled, priority flags
[ https://issues.apache.org/jira/browse/RANGER-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3269: - Fix Version/s: 2.2.0 3.0.0 > [Ranger Audits UI] Long policy names get overlapped with enabled, priority > flags > -- > > Key: RANGER-3269 > URL: https://issues.apache.org/jira/browse/RANGER-3269 > Project: Ranger > Issue Type: Improvement > Components: audit >Affects Versions: 2.2.0 >Reporter: Abhishek Shukla >Assignee: Nitin Galave >Priority: Minor > Fix For: 3.0.0, 2.2.0 > > Attachments: 0001-RANGER-3269.patch, Policy detail page in audits.png > > > Observed that with long policy names, the policy details page in the audits > UI, the policy name and policy enabled, priority flags are getting overlapped > with each other. > Attached screenshot. > Is it possible to wrap the policy name in multiple lines from the UI side? > cc [~nitin.galave] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3269) [Ranger Audits UI] Long policy names get overlapped with enabled, priority flags
[ https://issues.apache.org/jira/browse/RANGER-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346273#comment-17346273 ] Nitin Galave commented on RANGER-3269: -- Committed to [Apache-master|https://github.com/apache/ranger/commit/8328f56fb15c24913520ae745858e2a47e317956] branch. Committed to [ranger-2.2|https://github.com/apache/ranger/commit/de3474c9b4ee8ab790ab3ad2a782baf5163fdd95] branch. > [Ranger Audits UI] Long policy names get overlapped with enabled, priority > flags > -- > > Key: RANGER-3269 > URL: https://issues.apache.org/jira/browse/RANGER-3269 > Project: Ranger > Issue Type: Improvement > Components: audit >Affects Versions: 2.2.0 >Reporter: Abhishek Shukla >Assignee: Nitin Galave >Priority: Minor > Attachments: 0001-RANGER-3269.patch, Policy detail page in audits.png > > > Observed that with long policy names, the policy details page in the audits > UI, the policy name and policy enabled, priority flags are getting overlapped > with each other. > Attached screenshot. > Is it possible to wrap the policy name in multiple lines from the UI side? > cc [~nitin.galave] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3260) Update default hdfs audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3260:
-
Fix Version/s: 2.2.0
3.0.0
> Update default hdfs audit filters to filter out unwanted audits
> ---
>
> Key: RANGER-3260
> URL: https://issues.apache.org/jira/browse/RANGER-3260
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
>
>
> Can we update the default hdfs audit filters as follows:
> This will filter out hdfs audits related to hdfs, hue, oozie, spark, mapred,
> hbase service users access audits.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "actions":[
> "delete",
> "rename"
> ],
> "isAudited":true
> },
> {
> "users":[
> "hdfs"
> ],
> "actions":[
> "listStatus",
> "getfileinfo",
> "listCachePools",
> "listCacheDirectives",
> "listCorruptFileBlocks",
> "monitorHealth",
> "rollEditLog",
> "open"
> ],
> "isAudited":false
> },
> {
> "users":[
> "oozie"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/oozie/share/lib"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "spark"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/spark/applicationHistory"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "hue"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/hue"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "resources":{
> "path":{
> "values":[
> "/hbase"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "mapred"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/history"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "actions":[
> "getfileinfo"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3258) Update default hbase audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3258:
-
Fix Version/s: 2.2.0
3.0.0
> Update default hbase audit filters to filter out unwanted audits
>
>
> Key: RANGER-3258
> URL: https://issues.apache.org/jira/browse/RANGER-3258
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
>
>
> Can we update the default HBase audit filters as follows:
> This will filter out HBase audits related to default, hbase, atlas_janus,
> ATLAS_ENTITY_AUDIT_EVENTS table access by hbase service user.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "table":{
> "values":[
> "*-ROOT-*",
> "*.META.*",
> "*_acl_*",
> "hbase:meta",
> "hbase:acl",
> "default",
> "hbase"
> ]
> }
> },
> "users":[
> "hbase"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "table":{
> "values":[
> "atlas_janus",
> "ATLAS_ENTITY_AUDIT_EVENTS"
> ]
> },
> "column-family":{
> "values":[
> "*"
> ]
> },
> "column":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "hbase"
> ],
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "actions":[
> "balance"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3257) Update default kafka audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3257:
-
Fix Version/s: 2.2.0
3.0.0
> Update default kafka audit filters to filter out unwanted audits
>
>
> Key: RANGER-3257
> URL: https://issues.apache.org/jira/browse/RANGER-3257
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
>
>
> Can we update the default Kafka audit filters as follows:
> This will filter out Kafka audits related to ATLAS_SPARK_HOOK, topic describe
> action, etc
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES",
> "ATLAS_HOOK",
> "ATLAS_SPARK_HOOK"
> ]
> }
> },
> "users":[
> "atlas"
> ],
> "actions":[
> "describe",
> "publish",
> "consume"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_HOOK"
> ]
> }
> },
> "users":[
> "hive",
> "hbase",
> "impala",
> "nifi"
> ],
> "actions":[
> "publish",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES"
> ]
> }
> },
> "users":[
> "rangertagsync"
> ],
> "actions":[
> "consume",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "consumergroup":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "rangertagsync"
> ],
> "actions":[
> "consume"
> ],
> "isAudited":false
> },
> {
> "users":[
> "kafka"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3258) Update default hbase audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3258:
-
Attachment: 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
> Update default hbase audit filters to filter out unwanted audits
>
>
> Key: RANGER-3258
> URL: https://issues.apache.org/jira/browse/RANGER-3258
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
> Attachments:
> 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
>
>
> Can we update the default HBase audit filters as follows:
> This will filter out HBase audits related to default, hbase, atlas_janus,
> ATLAS_ENTITY_AUDIT_EVENTS table access by hbase service user.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "table":{
> "values":[
> "*-ROOT-*",
> "*.META.*",
> "*_acl_*",
> "hbase:meta",
> "hbase:acl",
> "default",
> "hbase"
> ]
> }
> },
> "users":[
> "hbase"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "table":{
> "values":[
> "atlas_janus",
> "ATLAS_ENTITY_AUDIT_EVENTS"
> ]
> },
> "column-family":{
> "values":[
> "*"
> ]
> },
> "column":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "hbase"
> ],
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "actions":[
> "balance"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3260) Update default hdfs audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3260:
-
Attachment: 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
> Update default hdfs audit filters to filter out unwanted audits
> ---
>
> Key: RANGER-3260
> URL: https://issues.apache.org/jira/browse/RANGER-3260
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
> Attachments:
> 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
>
>
> Can we update the default hdfs audit filters as follows:
> This will filter out hdfs audits related to hdfs, hue, oozie, spark, mapred,
> hbase service users access audits.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "actions":[
> "delete",
> "rename"
> ],
> "isAudited":true
> },
> {
> "users":[
> "hdfs"
> ],
> "actions":[
> "listStatus",
> "getfileinfo",
> "listCachePools",
> "listCacheDirectives",
> "listCorruptFileBlocks",
> "monitorHealth",
> "rollEditLog",
> "open"
> ],
> "isAudited":false
> },
> {
> "users":[
> "oozie"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/oozie/share/lib"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "spark"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/spark/applicationHistory"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "hue"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/hue"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "resources":{
> "path":{
> "values":[
> "/hbase"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "mapred"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/history"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "actions":[
> "getfileinfo"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3257) Update default kafka audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave updated RANGER-3257:
-
Attachment: 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
> Update default kafka audit filters to filter out unwanted audits
>
>
> Key: RANGER-3257
> URL: https://issues.apache.org/jira/browse/RANGER-3257
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
> Attachments:
> 0001-RANGER-3260-3258-3257-Update-default-audit-filters-f.patch
>
>
> Can we update the default Kafka audit filters as follows:
> This will filter out Kafka audits related to ATLAS_SPARK_HOOK, topic describe
> action, etc
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES",
> "ATLAS_HOOK",
> "ATLAS_SPARK_HOOK"
> ]
> }
> },
> "users":[
> "atlas"
> ],
> "actions":[
> "describe",
> "publish",
> "consume"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_HOOK"
> ]
> }
> },
> "users":[
> "hive",
> "hbase",
> "impala",
> "nifi"
> ],
> "actions":[
> "publish",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES"
> ]
> }
> },
> "users":[
> "rangertagsync"
> ],
> "actions":[
> "consume",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "consumergroup":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "rangertagsync"
> ],
> "actions":[
> "consume"
> ],
> "isAudited":false
> },
> {
> "users":[
> "kafka"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-3258) Update default hbase audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342425#comment-17342425
]
Nitin Galave commented on RANGER-3258:
--
Committed to
[apache-master|https://github.com/apache/ranger/commit/fb00ef4a2d794c0d837702a3817cc14aa69b1920]
branch.
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/62c9aeca807bd056c69a4b902db32a962c13590a]
branch.
> Update default hbase audit filters to filter out unwanted audits
>
>
> Key: RANGER-3258
> URL: https://issues.apache.org/jira/browse/RANGER-3258
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
>
> Can we update the default HBase audit filters as follows:
> This will filter out HBase audits related to default, hbase, atlas_janus,
> ATLAS_ENTITY_AUDIT_EVENTS table access by hbase service user.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "table":{
> "values":[
> "*-ROOT-*",
> "*.META.*",
> "*_acl_*",
> "hbase:meta",
> "hbase:acl",
> "default",
> "hbase"
> ]
> }
> },
> "users":[
> "hbase"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "table":{
> "values":[
> "atlas_janus",
> "ATLAS_ENTITY_AUDIT_EVENTS"
> ]
> },
> "column-family":{
> "values":[
> "*"
> ]
> },
> "column":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "hbase"
> ],
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "actions":[
> "balance"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-3260) Update default hdfs audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342424#comment-17342424
]
Nitin Galave commented on RANGER-3260:
--
Committed to
[apache-master|https://github.com/apache/ranger/commit/fb00ef4a2d794c0d837702a3817cc14aa69b1920]
branch.
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/62c9aeca807bd056c69a4b902db32a962c13590a]
branch.
> Update default hdfs audit filters to filter out unwanted audits
> ---
>
> Key: RANGER-3260
> URL: https://issues.apache.org/jira/browse/RANGER-3260
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
>
> Can we update the default hdfs audit filters as follows:
> This will filter out hdfs audits related to hdfs, hue, oozie, spark, mapred,
> hbase service users access audits.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "actions":[
> "delete",
> "rename"
> ],
> "isAudited":true
> },
> {
> "users":[
> "hdfs"
> ],
> "actions":[
> "listStatus",
> "getfileinfo",
> "listCachePools",
> "listCacheDirectives",
> "listCorruptFileBlocks",
> "monitorHealth",
> "rollEditLog",
> "open"
> ],
> "isAudited":false
> },
> {
> "users":[
> "oozie"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/oozie/share/lib"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "spark"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/spark/applicationHistory"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "hue"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/hue"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "resources":{
> "path":{
> "values":[
> "/hbase"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "users":[
> "mapred"
> ],
> "resources":{
> "path":{
> "values":[
> "/user/history"
> ],
> "isRecursive":true
> }
> },
> "isAudited":false
> },
> {
> "actions":[
> "getfileinfo"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (RANGER-3257) Update default kafka audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342423#comment-17342423
]
Nitin Galave edited comment on RANGER-3257 at 5/11/21, 8:54 AM:
Committed to
[apache-master|https://github.com/apache/ranger/commit/fb00ef4a2d794c0d837702a3817cc14aa69b1920]
branch.
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/62c9aeca807bd056c69a4b902db32a962c13590a]
branch.
was (Author: nitin.galave):
Committed to
[apache-master|https://github.com/apache/ranger/commit/fb00ef4a2d794c0d837702a3817cc14aa69b1920]
branch.
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/62c9aeca807bd056c69a4b902db32a962c13590a]
branch.
> Update default kafka audit filters to filter out unwanted audits
>
>
> Key: RANGER-3257
> URL: https://issues.apache.org/jira/browse/RANGER-3257
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
>
> Can we update the default Kafka audit filters as follows:
> This will filter out Kafka audits related to ATLAS_SPARK_HOOK, topic describe
> action, etc
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES",
> "ATLAS_HOOK",
> "ATLAS_SPARK_HOOK"
> ]
> }
> },
> "users":[
> "atlas"
> ],
> "actions":[
> "describe",
> "publish",
> "consume"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_HOOK"
> ]
> }
> },
> "users":[
> "hive",
> "hbase",
> "impala",
> "nifi"
> ],
> "actions":[
> "publish",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES"
> ]
> }
> },
> "users":[
> "rangertagsync"
> ],
> "actions":[
> "consume",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "consumergroup":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "rangertagsync"
> ],
> "actions":[
> "consume"
> ],
> "isAudited":false
> },
> {
> "users":[
> "kafka"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-3257) Update default kafka audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342423#comment-17342423
]
Nitin Galave commented on RANGER-3257:
--
Committed to
[apache-master|https://github.com/apache/ranger/commit/fb00ef4a2d794c0d837702a3817cc14aa69b1920]
branch.
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/62c9aeca807bd056c69a4b902db32a962c13590a]
branch.
> Update default kafka audit filters to filter out unwanted audits
>
>
> Key: RANGER-3257
> URL: https://issues.apache.org/jira/browse/RANGER-3257
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
>
> Can we update the default Kafka audit filters as follows:
> This will filter out Kafka audits related to ATLAS_SPARK_HOOK, topic describe
> action, etc
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES",
> "ATLAS_HOOK",
> "ATLAS_SPARK_HOOK"
> ]
> }
> },
> "users":[
> "atlas"
> ],
> "actions":[
> "describe",
> "publish",
> "consume"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_HOOK"
> ]
> }
> },
> "users":[
> "hive",
> "hbase",
> "impala",
> "nifi"
> ],
> "actions":[
> "publish",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "topic":{
> "values":[
> "ATLAS_ENTITIES"
> ]
> }
> },
> "users":[
> "rangertagsync"
> ],
> "actions":[
> "consume",
> "describe"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "consumergroup":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "rangertagsync"
> ],
> "actions":[
> "consume"
> ],
> "isAudited":false
> },
> {
> "users":[
> "kafka"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (RANGER-3258) Update default hbase audit filters to filter out unwanted audits
[
https://issues.apache.org/jira/browse/RANGER-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave reassigned RANGER-3258:
Assignee: Mateen Mansoori (was: Nitin Galave)
> Update default hbase audit filters to filter out unwanted audits
>
>
> Key: RANGER-3258
> URL: https://issues.apache.org/jira/browse/RANGER-3258
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.2.0
>Reporter: Abhishek Shukla
>Assignee: Mateen Mansoori
>Priority: Major
>
> Can we update the default HBase audit filters as follows:
> This will filter out HBase audits related to default, hbase, atlas_janus,
> ATLAS_ENTITY_AUDIT_EVENTS table access by hbase service user.
> {code:java}
> [
> {
> "accessResult":"DENIED",
> "isAudited":true
> },
> {
> "resources":{
> "table":{
> "values":[
> "*-ROOT-*",
> "*.META.*",
> "*_acl_*",
> "hbase:meta",
> "hbase:acl",
> "default",
> "hbase"
> ]
> }
> },
> "users":[
> "hbase"
> ],
> "isAudited":false
> },
> {
> "resources":{
> "table":{
> "values":[
> "atlas_janus",
> "ATLAS_ENTITY_AUDIT_EVENTS"
> ]
> },
> "column-family":{
> "values":[
> "*"
> ]
> },
> "column":{
> "values":[
> "*"
> ]
> }
> },
> "users":[
> "atlas",
> "hbase"
> ],
> "isAudited":false
> },
> {
> "users":[
> "hbase"
> ],
> "actions":[
> "balance"
> ],
> "isAudited":false
> }
> ]
> {code}
> cc [~dineshkumar-yadav]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
