[jira] [Assigned] (RANGER-806) Java cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-806: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > Java cli utility to delete users from

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Summary: Ranger cli utility to delete users from Ranger DB (was: Java cli utility to delete u

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Description: *Problem Statement* As of now, Delete Users feature is not available in Ranger UI

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Attachment: RANGER-806-2.patch Proposed Solution: This Patch provides a Python utility that us

[jira] [Assigned] (RANGER-271) Script and process to migrate existing audit from RDBMS to Solr

[ https://issues.apache.org/jira/browse/RANGER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-271: -- Assignee: Pradeep Agrawal (was: Don Bosco Durai) > Script and process to migrate exist

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Attachment: RANGER-806-3.patch > Ranger cli utility to delete users from Ranger DB > -

[jira] [Updated] (RANGER-863) Make parameters like maxHttpHeaderSize configurable for EmbeddedServer

[ https://issues.apache.org/jira/browse/RANGER-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-863: --- Attachment: RANGER-863-1.patch > Make parameters like maxHttpHeaderSize configurable for Embed

[jira] [Commented] (RANGER-863) Make parameters like maxHttpHeaderSize configurable for EmbeddedServer

[ https://issues.apache.org/jira/browse/RANGER-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177218#comment-15177218 ] Pradeep Agrawal commented on RANGER-863: **Problem Statement :** Parameters like m

[jira] [Commented] (RANGER-271) Script and process to migrate existing audit from RDBMS to Solr

[ https://issues.apache.org/jira/browse/RANGER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179284#comment-15179284 ] Pradeep Agrawal commented on RANGER-271: *Proposed Solution:* Make sure below give

[jira] [Updated] (RANGER-271) Script and process to migrate existing audit from RDBMS to Solr

[ https://issues.apache.org/jira/browse/RANGER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-271: --- Attachment: RANGER-271-1.patch > Script and process to migrate existing audit from RDBMS to So

[jira] [Updated] (RANGER-271) Script and process to migrate existing audit from RDBMS to Solr

[ https://issues.apache.org/jira/browse/RANGER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-271: --- Attachment: (was: RANGER-271-1.patch) > Script and process to migrate existing audit from

[jira] [Updated] (RANGER-271) Script and process to migrate existing audit from RDBMS to Solr

[ https://issues.apache.org/jira/browse/RANGER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-271: --- Attachment: RANGER-271-3.patch > Script and process to migrate existing audit from RDBMS to So

[jira] [Created] (RANGER-875) Restrict Grantor privileges of Ranger db user for Oracle DB Flavour

Pradeep Agrawal created RANGER-875: -- Summary: Restrict Grantor privileges of Ranger db user for Oracle DB Flavour Key: RANGER-875 URL: https://issues.apache.org/jira/browse/RANGER-875 Project: Ranger

[jira] [Updated] (RANGER-875) Restrict Grantor privileges of Ranger db user for Oracle DB Flavour

[ https://issues.apache.org/jira/browse/RANGER-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-875: --- Attachment: RANGER-875-1.patch > Restrict Grantor privileges of Ranger db user for Oracle DB F

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Attachment: (was: RANGER-806-2.patch) > Ranger cli utility to delete users from Ranger DB

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Attachment: (was: RANGER-806-3.patch) > Ranger cli utility to delete users from Ranger DB

[jira] [Updated] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-806: --- Attachment: RANGER-806-8.patch > Ranger cli utility to delete users from Ranger DB > -

[jira] [Updated] (RANGER-888) Provide support to delete Users and Groups from Ranger Admin UI

[ https://issues.apache.org/jira/browse/RANGER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-888: --- Attachment: RANGER-888-1.patch > Provide support to delete Users and Groups from Ranger Admin

[jira] [Created] (RANGER-888) Provide support to delete Users and Groups from Ranger Admin UI

Pradeep Agrawal created RANGER-888: -- Summary: Provide support to delete Users and Groups from Ranger Admin UI Key: RANGER-888 URL: https://issues.apache.org/jira/browse/RANGER-888 Project: Ranger

[jira] [Commented] (RANGER-806) Ranger cli utility to delete users from Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197259#comment-15197259 ] Pradeep Agrawal commented on RANGER-806: Patch committed to master branch : https

[jira] [Commented] (RANGER-882) Policy engine initialization should handle incorrect values in policies

[ https://issues.apache.org/jira/browse/RANGER-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208146#comment-15208146 ] Pradeep Agrawal commented on RANGER-882: Third commit to handle null and empty res

[jira] [Commented] (RANGER-888) Provide support to delete Users and Groups from Ranger Admin UI

[ https://issues.apache.org/jira/browse/RANGER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208961#comment-15208961 ] Pradeep Agrawal commented on RANGER-888: Committed to master branch : https://git

[jira] [Created] (RANGER-896) Add Maria DB support for Ranger and Ranger KMS

Pradeep Agrawal created RANGER-896: -- Summary: Add Maria DB support for Ranger and Ranger KMS Key: RANGER-896 URL: https://issues.apache.org/jira/browse/RANGER-896 Project: Ranger Issue Type:

[jira] [Updated] (RANGER-896) Add Maria DB support for Ranger and Ranger KMS

[ https://issues.apache.org/jira/browse/RANGER-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-896: --- Attachment: RANGER-896-1.patch Ranger is working fine with MariaDB 5.5.48, 10.0.24 and MySQL 5

[jira] [Assigned] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-900: -- Assignee: Pradeep Agrawal (was: Velmurugan Periasamy) > Remove support for DB based au

[jira] [Created] (RANGER-910) Improve db and java patches execution logic to make that more robust

Pradeep Agrawal created RANGER-910: -- Summary: Improve db and java patches execution logic to make that more robust Key: RANGER-910 URL: https://issues.apache.org/jira/browse/RANGER-910 Project: Rang

[jira] [Commented] (RANGER-896) Add Maria DB support for Ranger and Ranger KMS

[ https://issues.apache.org/jira/browse/RANGER-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223686#comment-15223686 ] Pradeep Agrawal commented on RANGER-896: Patch committed in master branch : https

[jira] [Updated] (RANGER-910) Improve db and java patches execution logic to make that more robust

[ https://issues.apache.org/jira/browse/RANGER-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-910: --- Attachment: RANGER-910-1.patch > Improve db and java patches execution logic to make that more

[jira] [Updated] (RANGER-908) Ranger policy model to support row-filtering

[ https://issues.apache.org/jira/browse/RANGER-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-908: --- Attachment: 0001-RANGER-908-Ranger-policy-model-to-support-data-maski.patch > Ranger policy mo

[jira] [Updated] (RANGER-910) Improve db and java patches execution logic to make that more robust

[ https://issues.apache.org/jira/browse/RANGER-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-910: --- Attachment: (was: RANGER-910-1.patch) > Improve db and java patches execution logic to mak

[jira] [Commented] (RANGER-910) Improve db and java patches execution logic to make that more robust

[ https://issues.apache.org/jira/browse/RANGER-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229625#comment-15229625 ] Pradeep Agrawal commented on RANGER-910: Committed to 0.5 branch : https://github

[jira] [Commented] (RANGER-910) Improve db and java patches execution logic to make that more robust

[ https://issues.apache.org/jira/browse/RANGER-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229627#comment-15229627 ] Pradeep Agrawal commented on RANGER-910: Committed to master branch : https://git

[jira] [Updated] (RANGER-910) Improve db and java patches execution logic to make that more robust

[ https://issues.apache.org/jira/browse/RANGER-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-910: --- Attachment: RANGER-910-2.patch > Improve db and java patches execution logic to make that more

[jira] [Updated] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-900: --- Attachment: RANGER-900-1.patch > Remove support for DB based auditing > --

[jira] [Created] (RANGER-921) Improve implementation of internal SQL calls and make it more generic

Pradeep Agrawal created RANGER-921: -- Summary: Improve implementation of internal SQL calls and make it more generic Key: RANGER-921 URL: https://issues.apache.org/jira/browse/RANGER-921 Project: Rang

[jira] [Updated] (RANGER-921) Improve implementation of internal SQL calls and make it more generic

[ https://issues.apache.org/jira/browse/RANGER-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-921: --- Description: Improve implementation of internal SQL calls and make it more generic in order to

[jira] [Updated] (RANGER-921) Improve implementation of internal SQL calls and make it more generic

[ https://issues.apache.org/jira/browse/RANGER-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-921: --- Attachment: RANGER-921-1.patch > Improve implementation of internal SQL calls and make it more

[jira] [Updated] (RANGER-921) Improve implementation of internal SQL calls and make it more generic

[ https://issues.apache.org/jira/browse/RANGER-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-921: --- Attachment: RANGER-921-1-branch-0.5.patch > Improve implementation of internal SQL calls and m

[jira] [Updated] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-900: --- Attachment: RANGER-900-2.patch > Remove support for DB based auditing > --

[jira] [Commented] (RANGER-341) request_data and request_path columns are short

[ https://issues.apache.org/jira/browse/RANGER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240719#comment-15240719 ] Pradeep Agrawal commented on RANGER-341: request_data and request_path columns siz

[jira] [Resolved] (RANGER-341) request_data and request_path columns are short

[ https://issues.apache.org/jira/browse/RANGER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-341. Resolution: Fixed > request_data and request_path columns are short > --

[jira] [Resolved] (RANGER-463) Unable to apply patch:PatchPasswordEncryption_J10001.class.

[ https://issues.apache.org/jira/browse/RANGER-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-463. Resolution: Not A Bug > Unable to apply patch:PatchPasswordEncryption_J10001.class. > -

[jira] [Updated] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-900: --- Attachment: RANGER-900-3.patch > Remove support for DB based auditing > --

[jira] [Updated] (RANGER-913) Improvements on Reports page in Ranger Admin

[ https://issues.apache.org/jira/browse/RANGER-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-913: --- Attachment: RANGER-913-2.patch Patch RANGER-913-2.patch for PMD violation fix > Improvements

[jira] [Updated] (RANGER-888) Provide support to delete Users and Groups from Ranger Admin UI

[ https://issues.apache.org/jira/browse/RANGER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-888: --- Attachment: RANGER-888-3-branch-0.5.patch Patch for 0.5 branch. > Provide support to delete U

[jira] [Commented] (RANGER-888) Provide support to delete Users and Groups from Ranger Admin UI

[ https://issues.apache.org/jira/browse/RANGER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242915#comment-15242915 ] Pradeep Agrawal commented on RANGER-888: Committed to 0.5 branch : https://github

[jira] [Assigned] (RANGER-710) Add a permission for 'Tag Based Policies'

[ https://issues.apache.org/jira/browse/RANGER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-710: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > Add a permission for 'Tag Based Polici

[jira] [Updated] (RANGER-710) Add a permission for 'Tag Based Policies'

[ https://issues.apache.org/jira/browse/RANGER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-710: --- Fix Version/s: 0.6.0 > Add a permission for 'Tag Based Policies' > ---

[jira] [Updated] (RANGER-710) Add a permission for 'Tag Based Policies'

[ https://issues.apache.org/jira/browse/RANGER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-710: --- Attachment: RANGER-710-1.patch > Add a permission for 'Tag Based Policies' > -

[jira] [Assigned] (RANGER-255) Email Address discrepancy

[ https://issues.apache.org/jira/browse/RANGER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-255: -- Assignee: Pradeep Agrawal > Email Address discrepancy > - > >

[jira] [Updated] (RANGER-255) Email Address discrepancy

[ https://issues.apache.org/jira/browse/RANGER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-255: --- Fix Version/s: 0.5.0 > Email Address discrepancy > - > >

[jira] [Updated] (RANGER-255) Email Address discrepancy

[ https://issues.apache.org/jira/browse/RANGER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-255: --- Fix Version/s: 0.6.0 > Email Address discrepancy > - > >

[jira] [Created] (RANGER-934) Ranger should use released version of EclipseLink

Pradeep Agrawal created RANGER-934: -- Summary: Ranger should use released version of EclipseLink Key: RANGER-934 URL: https://issues.apache.org/jira/browse/RANGER-934 Project: Ranger Issue Ty

[jira] [Created] (RANGER-935) Persistence.xml file should have mapping of all Entity classes

Pradeep Agrawal created RANGER-935: -- Summary: Persistence.xml file should have mapping of all Entity classes Key: RANGER-935 URL: https://issues.apache.org/jira/browse/RANGER-935 Project: Ranger

[jira] [Updated] (RANGER-934) Ranger should use released version of EclipseLink

[ https://issues.apache.org/jira/browse/RANGER-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-934: --- Attachment: RANGER-934-1.patch > Ranger should use released version of EclipseLink > -

[jira] [Updated] (RANGER-935) Persistence.xml file should have mapping of all Entity classes

[ https://issues.apache.org/jira/browse/RANGER-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-935: --- Attachment: RANGER-935-1.patch > Persistence.xml file should have mapping of all Entity classe

[jira] [Updated] (RANGER-255) Email Address discrepancy

[ https://issues.apache.org/jira/browse/RANGER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-255: --- Attachment: RANGER-255-1.patch > Email Address discrepancy > - > >

[jira] [Updated] (RANGER-255) Email Address discrepancy

[ https://issues.apache.org/jira/browse/RANGER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-255: --- Fix Version/s: (was: 0.5.0) > Email Address discrepancy > - > >

[jira] [Updated] (RANGER-934) Ranger should use released version of EclipseLink

[ https://issues.apache.org/jira/browse/RANGER-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-934: --- Attachment: (was: RANGER-934-1.patch) > Ranger should use released version of EclipseLink

[jira] [Updated] (RANGER-934) Ranger should use released version of EclipseLink

[ https://issues.apache.org/jira/browse/RANGER-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-934: --- Description: Currently Ranger is using EclipseLink 2.5.2-M1 version, Consider using EclipseLi

[jira] [Updated] (RANGER-934) Ranger should use released version of EclipseLink

[ https://issues.apache.org/jira/browse/RANGER-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-934: --- Attachment: RANGER-934-1.patch > Ranger should use released version of EclipseLink > -

[jira] [Updated] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-900: --- Attachment: (was: RANGER-900-2.patch) > Remove support for DB based auditing > ---

[jira] [Updated] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-900: --- Attachment: (was: RANGER-900-1.patch) > Remove support for DB based auditing > ---

[jira] [Updated] (RANGER-900) Remove support for DB based auditing

[ https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-900: --- Attachment: RANGER-900-4.patch > Remove support for DB based auditing > --

[jira] [Created] (RANGER-951) Modify ranger-admin to put stackdef for specified components

Pradeep Agrawal created RANGER-951: -- Summary: Modify ranger-admin to put stackdef for specified components Key: RANGER-951 URL: https://issues.apache.org/jira/browse/RANGER-951 Project: Ranger

[jira] [Created] (RANGER-952) Tagadmin user name should be configurable in tagsync module

Pradeep Agrawal created RANGER-952: -- Summary: Tagadmin user name should be configurable in tagsync module Key: RANGER-952 URL: https://issues.apache.org/jira/browse/RANGER-952 Project: Ranger

[jira] [Created] (RANGER-953) Tag Based policies menu is not appearing for 'ADMIN' role users after upgrade from 0.5

Pradeep Agrawal created RANGER-953: -- Summary: Tag Based policies menu is not appearing for 'ADMIN' role users after upgrade from 0.5 Key: RANGER-953 URL: https://issues.apache.org/jira/browse/RANGER-953

[jira] [Updated] (RANGER-951) Modify ranger-admin to put stackdef for specified components

[ https://issues.apache.org/jira/browse/RANGER-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-951: --- Attachment: RANGER-951-1.patch > Modify ranger-admin to put stackdef for specified components

[jira] [Updated] (RANGER-953) Tag Based policies menu is not appearing for 'ADMIN' role users after upgrade from 0.5

[ https://issues.apache.org/jira/browse/RANGER-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-953: --- Attachment: RANGER-953-1.patch > Tag Based policies menu is not appearing for 'ADMIN' role use

[jira] [Updated] (RANGER-952) Tagadmin user name should be configurable in tagsync module

[ https://issues.apache.org/jira/browse/RANGER-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-952: --- Attachment: RANGER-952-1.patch > Tagadmin user name should be configurable in tagsync module >

[jira] [Assigned] (RANGER-460) Users / Groups Get and Set Visibility rest api should be allowed only for users with admin role.

[ https://issues.apache.org/jira/browse/RANGER-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-460: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > Users / Groups Get and Set Visibility

[jira] [Assigned] (RANGER-719) Audit in RangerAdmin doesn't show latest audits in UI if server is on different timezone

[ https://issues.apache.org/jira/browse/RANGER-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-719: -- Assignee: Pradeep Agrawal > Audit in RangerAdmin doesn't show latest audits in UI if se

[jira] [Assigned] (RANGER-631) audit log is not present for deleting user

[ https://issues.apache.org/jira/browse/RANGER-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-631: -- Assignee: Pradeep Agrawal (was: Deepak Sharma) > audit log is not present for deleting

[jira] [Updated] (RANGER-631) audit log is not present for deleting user

[ https://issues.apache.org/jira/browse/RANGER-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-631: --- Attachment: solved.png Please check attached solved.png file, this has been resolved with comm

[jira] [Updated] (RANGER-951) Modify ranger-admin to put stackdef for specified components

[ https://issues.apache.org/jira/browse/RANGER-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-951: --- Attachment: RANGER-951-4.patch > Modify ranger-admin to put stackdef for specified components

[jira] [Updated] (RANGER-953) Tag Based policies menu is not appearing for 'ADMIN' role users after upgrade from 0.5

[ https://issues.apache.org/jira/browse/RANGER-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-953: --- Attachment: RANGER-953-2.patch > Tag Based policies menu is not appearing for 'ADMIN' role use

[jira] [Updated] (RANGER-951) Modify ranger-admin to put stackdef for specified components

[ https://issues.apache.org/jira/browse/RANGER-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-951: --- Attachment: (was: RANGER-951-1.patch) > Modify ranger-admin to put stackdef for specified

[jira] [Updated] (RANGER-953) Tag Based policies menu is not appearing for 'ADMIN' role users after upgrade from 0.5

[ https://issues.apache.org/jira/browse/RANGER-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-953: --- Attachment: (was: RANGER-953-1.patch) > Tag Based policies menu is not appearing for 'ADMI

[jira] [Commented] (RANGER-255) Email Address discrepancy

[ https://issues.apache.org/jira/browse/RANGER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263818#comment-15263818 ] Pradeep Agrawal commented on RANGER-255: Committed to master branch : https://git

[jira] [Commented] (RANGER-951) Modify ranger-admin to put stackdef for specified components

[ https://issues.apache.org/jira/browse/RANGER-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263821#comment-15263821 ] Pradeep Agrawal commented on RANGER-951: Committed to master branch : https://git

[jira] [Created] (RANGER-965) Validate Audit DB to Solr Migration script from any previous version to 0.6 upgrade

Pradeep Agrawal created RANGER-965: -- Summary: Validate Audit DB to Solr Migration script from any previous version to 0.6 upgrade Key: RANGER-965 URL: https://issues.apache.org/jira/browse/RANGER-965

[jira] [Updated] (RANGER-965) Validate Audit DB to Solr Migration script from any previous version to 0.6 upgrade

[ https://issues.apache.org/jira/browse/RANGER-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-965: --- Attachment: RANGER-965-1.patch > Validate Audit DB to Solr Migration script from any previous

[jira] [Resolved] (RANGER-460) Users / Groups Get and Set Visibility rest api should be allowed only for users with admin role.

[ https://issues.apache.org/jira/browse/RANGER-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-460. Resolution: Fixed Issue has been fixed with RANGER-630 commit master branch : https://githu

[jira] [Created] (RANGER-984) Ranger Admin Install fails with "022-split-service-table.sql Import failed!"

Pradeep Agrawal created RANGER-984: -- Summary: Ranger Admin Install fails with "022-split-service-table.sql Import failed!" Key: RANGER-984 URL: https://issues.apache.org/jira/browse/RANGER-984 Projec

[jira] [Updated] (RANGER-984) Ranger Admin Install fails with "022-split-service-table.sql Import failed!"

[ https://issues.apache.org/jira/browse/RANGER-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-984: --- Attachment: RANGER-984-1.patch > Ranger Admin Install fails with "022-split-service-table.sql

[jira] [Updated] (RANGER-965) Validate Audit DB to Solr Migration script from any previous version to 0.6 upgrade

[ https://issues.apache.org/jira/browse/RANGER-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-965: --- Attachment: 0001-RANGER-965-3.patch > Validate Audit DB to Solr Migration script from any prev

[jira] [Resolved] (RANGER-719) Audit in RangerAdmin doesn't show latest audits in UI if server is on different timezone

[ https://issues.apache.org/jira/browse/RANGER-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-719. Resolution: Duplicate Fix Version/s: 0.6.0 0.5.0 > Audit in Ranger

[jira] [Assigned] (RANGER-443) ncorrect http status code for missing ranger portal permission

[ https://issues.apache.org/jira/browse/RANGER-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-443: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > ncorrect http status code for missing

[jira] [Assigned] (RANGER-411) Review and update unit tests

[ https://issues.apache.org/jira/browse/RANGER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-411: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > Review and update unit tests > ---

[jira] [Assigned] (RANGER-414) Resource name is not easily readable in Ranger access logs

[ https://issues.apache.org/jira/browse/RANGER-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-414: -- Assignee: Pradeep Agrawal > Resource name is not easily readable in Ranger access logs

[jira] [Assigned] (RANGER-413) Multiple audit entries are stored in Ranger database for HDFS plugin for a single operation

[ https://issues.apache.org/jira/browse/RANGER-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-413: -- Assignee: Pradeep Agrawal > Multiple audit entries are stored in Ranger database for HD

[jira] [Assigned] (RANGER-456) Audit page shows 'Page not found (404)' after renaming a service (repository)

[ https://issues.apache.org/jira/browse/RANGER-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-456: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > Audit page shows 'Page not found (404)

[jira] [Assigned] (RANGER-480) Need access control on REST API based on permission model

[ https://issues.apache.org/jira/browse/RANGER-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-480: -- Assignee: Pradeep Agrawal (was: Gautam Borad) > Need access control on REST API based

[jira] [Updated] (RANGER-899) Problem Changing/Updating emailAddress of logged in user using API: "{userId}/emailchange" of class org.apache.ranger.rest.UserREST.java

[ https://issues.apache.org/jira/browse/RANGER-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-899: --- Assignee: Bryan Bende > Problem Changing/Updating emailAddress of logged in user using API: >

[jira] [Assigned] (RANGER-691) Ranger Admin shouldn't expect users to be sync'ed for authentication

[ https://issues.apache.org/jira/browse/RANGER-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-691: -- Assignee: Pradeep Agrawal > Ranger Admin shouldn't expect users to be sync'ed for authe

[jira] [Assigned] (RANGER-690) Ranger Admin doesn't show error if Audit Solr is down

[ https://issues.apache.org/jira/browse/RANGER-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-690: -- Assignee: Pradeep Agrawal > Ranger Admin doesn't show error if Audit Solr is down > ---

[jira] [Assigned] (RANGER-655) Review DB schema for max key length restrictions - MySQL

[ https://issues.apache.org/jira/browse/RANGER-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-655: -- Assignee: Pradeep Agrawal > Review DB schema for max key length restrictions - MySQL >

[jira] [Assigned] (RANGER-899) Problem Changing/Updating emailAddress of logged in user using API: "{userId}/emailchange" of class org.apache.ranger.rest.UserREST.java

[ https://issues.apache.org/jira/browse/RANGER-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-899: -- Assignee: Pradeep Agrawal (was: Bryan Bende) > Problem Changing/Updating emailAddress

[jira] [Resolved] (RANGER-480) Need access control on REST API based on permission model

[ https://issues.apache.org/jira/browse/RANGER-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-480. Resolution: Fixed > Need access control on REST API based on permission model >

[jira] [Commented] (RANGER-480) Need access control on REST API based on permission model

[ https://issues.apache.org/jira/browse/RANGER-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293341#comment-15293341 ] Pradeep Agrawal commented on RANGER-480: * Get AuditLogs (user-with-no-permission)

  1   2   3   4   >