[jira] [Created] (RANGER-4833) Upgrade from Bootbox.js to Bootprompt.js
Dhaval Rajpara created RANGER-4833: -- Summary: Upgrade from Bootbox.js to Bootprompt.js Key: RANGER-4833 URL: https://issues.apache.org/jira/browse/RANGER-4833 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 3.0.0, 2.5.0 Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Upgrade from Bootbox.js to Bootprompt.js -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4819) Proposal to Upgrade All React.js Dependent Libraries
Dhaval Rajpara created RANGER-4819: -- Summary: Proposal to Upgrade All React.js Dependent Libraries Key: RANGER-4819 URL: https://issues.apache.org/jira/browse/RANGER-4819 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Upgrading all dependent libraries for React.js in our project. This will ensure we are using the latest versions, improving security, performance, and compatibility with new features. # babel/traverse # axios # braces # follow-redirects # json5 # loader-utils # minimist # moment # terser # webpack # webpack-dev-middleware -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4774) Ranger react UI some modules shown hardcoded time zone string "Indian Standard Time"
[ https://issues.apache.org/jira/browse/RANGER-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852741#comment-17852741 ] Dhaval Rajpara commented on RANGER-4774: Patch committed to [Apache master|https://github.com/apache/ranger/commit/65fad025d908b280440dbca4c7a61de3fa8ef943] branch. > Ranger react UI some modules shown hardcoded time zone string "Indian > Standard Time" > - > > Key: RANGER-4774 > URL: https://issues.apache.org/jira/browse/RANGER-4774 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4774.patch > > > 1) UI popup showing details of an admin audit log seems to have hardcoded > string “Indian Standard Time” > 2)Some logs table header also have hardcoded string “Indian Standard Time” -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4774) Ranger react UI some modules shown hardcoded time zone string "Indian Standard Time"
[ https://issues.apache.org/jira/browse/RANGER-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4774: --- Fix Version/s: 3.0.0 > Ranger react UI some modules shown hardcoded time zone string "Indian > Standard Time" > - > > Key: RANGER-4774 > URL: https://issues.apache.org/jira/browse/RANGER-4774 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4774.patch > > > 1) UI popup showing details of an admin audit log seems to have hardcoded > string “Indian Standard Time” > 2)Some logs table header also have hardcoded string “Indian Standard Time” -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4774) Ranger react UI some modules shown hardcoded time zone string "Indian Standard Time"
[ https://issues.apache.org/jira/browse/RANGER-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4774: --- Attachment: 0001-RANGER-4774.patch > Ranger react UI some modules shown hardcoded time zone string "Indian > Standard Time" > - > > Key: RANGER-4774 > URL: https://issues.apache.org/jira/browse/RANGER-4774 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4774.patch > > > 1) UI popup showing details of an admin audit log seems to have hardcoded > string “Indian Standard Time” > 2)Some logs table header also have hardcoded string “Indian Standard Time” -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4643) Upgrade react-bootstrap library for GDS UI.
[ https://issues.apache.org/jira/browse/RANGER-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845881#comment-17845881 ] Dhaval Rajpara commented on RANGER-4643: Patch committed to [Apache master|https://github.com/apache/ranger/commit/bf114e65529aa0399b67e56da4ef74f14def8f63] branch. > Upgrade react-bootstrap library for GDS UI. > --- > > Key: RANGER-4643 > URL: https://issues.apache.org/jira/browse/RANGER-4643 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: > 0001-RANGER-4643-Upgrade-react-bootstrap-library-for-GDS-.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4785) Implement best coding practices for validating user input
[ https://issues.apache.org/jira/browse/RANGER-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4785: --- Attachment: 0001-RANGER-4785.patch > Implement best coding practices for validating user input > - > > Key: RANGER-4785 > URL: https://issues.apache.org/jira/browse/RANGER-4785 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4785.patch > > > Implement best coding practices for validating user input -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4785) Implement best coding practices for validating user input
Dhaval Rajpara created RANGER-4785: -- Summary: Implement best coding practices for validating user input Key: RANGER-4785 URL: https://issues.apache.org/jira/browse/RANGER-4785 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.4.0 Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Implement best coding practices for validating user input -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4774) Ranger react UI some modules shown hardcoded time zone string "Indian Standard Time"
Dhaval Rajpara created RANGER-4774: -- Summary: Ranger react UI some modules shown hardcoded time zone string "Indian Standard Time" Key: RANGER-4774 URL: https://issues.apache.org/jira/browse/RANGER-4774 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara 1) UI popup showing details of an admin audit log seems to have hardcoded string “Indian Standard Time” 2)Some logs table header also have hardcoded string “Indian Standard Time” -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4773) Implementing Individual Routing for All Tabs in Dataset and Datashare details view
[ https://issues.apache.org/jira/browse/RANGER-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4773: --- Description: 1) Enhancing the Details View of Dataset and Datashare by Introducing Individual Routing for Tabs Currently, the Details view of Dataset and Datashare lacks individual routing for its tabs, necessitating the implementation of such routing. By introducing router functionality, users will gain the benefit of direct navigation to specific tabs by simply copying and pasting the corresponding URL. This enhancement aims to improve user experience and streamline navigation within the Dataset and Datashare sections. 2) Currently, users sometimes experience difficulties when navigating back to the 'My Dataset' listing page, requiring multiple clicks of the back button. To enhance user experience and streamline navigation, we aim to optimize the functionality of the back button in this jira. CC : [~madhan] / [~dineshkumar-yadav] / [~mugdha.varadkar] was: 1) Enhancing the Details View of Dataset and Datashare by Introducing Individual Routing for Tabs Currently, the Details view of Dataset and Datashare lacks individual routing for its tabs, necessitating the implementation of such routing. By introducing router functionality, users will gain the benefit of direct navigation to specific tabs by simply copying and pasting the corresponding URL. This enhancement aims to improve user experience and streamline navigation within the Dataset and Datashare sections. 2) Currently, users sometimes experience difficulties when navigating back to the 'My Dataset' listing page, requiring multiple clicks of the back button. To enhance user experience and streamline navigation, we aim to optimize the functionality of the back button in this jira. > Implementing Individual Routing for All Tabs in Dataset and Datashare details > view > -- > > Key: RANGER-4773 > URL: https://issues.apache.org/jira/browse/RANGER-4773 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > 1) Enhancing the Details View of Dataset and Datashare by Introducing > Individual Routing for Tabs > Currently, the Details view of Dataset and Datashare lacks individual routing > for its tabs, necessitating the implementation of such routing. By > introducing router functionality, users will gain the benefit of direct > navigation to specific tabs by simply copying and pasting the corresponding > URL. This enhancement aims to improve user experience and streamline > navigation within the Dataset and Datashare sections. > 2) Currently, users sometimes experience difficulties when navigating back to > the 'My Dataset' listing page, requiring multiple clicks of the back button. > To enhance user experience and streamline navigation, we aim to optimize the > functionality of the back button in this jira. > CC : [~madhan] / [~dineshkumar-yadav] / [~mugdha.varadkar] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4773) Implementing Individual Routing for All Tabs in Dataset and Datashare details view
[ https://issues.apache.org/jira/browse/RANGER-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4773: --- Description: 1) Enhancing the Details View of Dataset and Datashare by Introducing Individual Routing for Tabs Currently, the Details view of Dataset and Datashare lacks individual routing for its tabs, necessitating the implementation of such routing. By introducing router functionality, users will gain the benefit of direct navigation to specific tabs by simply copying and pasting the corresponding URL. This enhancement aims to improve user experience and streamline navigation within the Dataset and Datashare sections. 2) Currently, users sometimes experience difficulties when navigating back to the 'My Dataset' listing page, requiring multiple clicks of the back button. To enhance user experience and streamline navigation, we aim to optimize the functionality of the back button in this jira. was: Enhancing the Details View of Dataset and Datashare by Introducing Individual Routing for Tabs Currently, the Details view of Dataset and Datashare lacks individual routing for its tabs, necessitating the implementation of such routing. By introducing router functionality, users will gain the benefit of direct navigation to specific tabs by simply copying and pasting the corresponding URL. This enhancement aims to improve user experience and streamline navigation within the Dataset and Datashare sections. > Implementing Individual Routing for All Tabs in Dataset and Datashare details > view > -- > > Key: RANGER-4773 > URL: https://issues.apache.org/jira/browse/RANGER-4773 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > 1) Enhancing the Details View of Dataset and Datashare by Introducing > Individual Routing for Tabs > Currently, the Details view of Dataset and Datashare lacks individual routing > for its tabs, necessitating the implementation of such routing. By > introducing router functionality, users will gain the benefit of direct > navigation to specific tabs by simply copying and pasting the corresponding > URL. This enhancement aims to improve user experience and streamline > navigation within the Dataset and Datashare sections. > 2) Currently, users sometimes experience difficulties when navigating back to > the 'My Dataset' listing page, requiring multiple clicks of the back button. > To enhance user experience and streamline navigation, we aim to optimize the > functionality of the back button in this jira. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4643) Upgrade react-bootstrap library for GDS UI.
[ https://issues.apache.org/jira/browse/RANGER-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4643: --- Attachment: 0001-RANGER-4643-Upgrade-react-bootstrap-library-for-GDS-.patch > Upgrade react-bootstrap library for GDS UI. > --- > > Key: RANGER-4643 > URL: https://issues.apache.org/jira/browse/RANGER-4643 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: > 0001-RANGER-4643-Upgrade-react-bootstrap-library-for-GDS-.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4680) Inconsistent resource lookup behaviour with newly created service
[ https://issues.apache.org/jira/browse/RANGER-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4680: --- Labels: ranger-react (was: ) > Inconsistent resource lookup behaviour with newly created service > - > > Key: RANGER-4680 > URL: https://issues.apache.org/jira/browse/RANGER-4680 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4680.patch > > > For newly created service, on policy create page, entering text in the > resource field doesn't trigger the corresponding resource lookup API. > Upon reloading the page the resource lookup api is getting called. > > Steps to repro: > 1) Create a new Hive service. > 2) Go to policy listing page of above created service > 3) Click on Add New Policy button for creating new policy. > 4) In Hive Database resource field enter some text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4699) Update the execution of setServiceDef call in App.jsx
[ https://issues.apache.org/jira/browse/RANGER-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4699: --- Attachment: 0001-RANGER-4699-Update-the-execution-of-setServiceDef-ca.patch > Update the execution of setServiceDef call in App.jsx > - > > Key: RANGER-4699 > URL: https://issues.apache.org/jira/browse/RANGER-4699 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: > 0001-RANGER-4699-Update-the-execution-of-setServiceDef-ca.patch > > > Need minor code update in executing the setServiceDef() call in App.jsx -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4699) Update the execution of setServiceDef call in App.jsx
[ https://issues.apache.org/jira/browse/RANGER-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4699: --- Attachment: (was: 0001-RANGER-4699.patch) > Update the execution of setServiceDef call in App.jsx > - > > Key: RANGER-4699 > URL: https://issues.apache.org/jira/browse/RANGER-4699 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: > 0001-RANGER-4699-Update-the-execution-of-setServiceDef-ca.patch > > > Need minor code update in executing the setServiceDef() call in App.jsx -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4680) Inconsistent resource lookup behaviour with newly created service
[ https://issues.apache.org/jira/browse/RANGER-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4680: --- Attachment: 0001-RANGER-4680.patch > Inconsistent resource lookup behaviour with newly created service > - > > Key: RANGER-4680 > URL: https://issues.apache.org/jira/browse/RANGER-4680 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4680.patch > > > For newly created service, on policy create page, entering text in the > resource field doesn't trigger the corresponding resource lookup API. > Upon reloading the page the resource lookup api is getting called. > > Steps to repro: > 1) Create a new Hive service. > 2) Go to policy listing page of above created service > 3) Click on Add New Policy button for creating new policy. > 4) In Hive Database resource field enter some text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4673) Pagination on the Ranger Admin - Plugin Status page
[ https://issues.apache.org/jira/browse/RANGER-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4673: --- Attachment: 0001-RANGER-4673.patch > Pagination on the Ranger Admin - Plugin Status page > --- > > Key: RANGER-4673 > URL: https://issues.apache.org/jira/browse/RANGER-4673 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4673.patch > > > The Ranger Admin UI's "Plugin Status" page does not offer pagination. > The UI shows only (the first random) 200 entries, we have no way to go to > next pages, and the ordering/sorting on columns is only a "client side" > sorting so some entries cannot be seen easily. (only if we search by Host > Name for example) > This is a usability issue with bigger clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4699) Update the execution of setServiceDef call in App.jsx
[ https://issues.apache.org/jira/browse/RANGER-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4699: --- Component/s: (was: admin) > Update the execution of setServiceDef call in App.jsx > - > > Key: RANGER-4699 > URL: https://issues.apache.org/jira/browse/RANGER-4699 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4699.patch > > > Need minor code update in executing the setServiceDef() call in App.jsx -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4699) Update the execution of setServiceDef call in App.jsx
[ https://issues.apache.org/jira/browse/RANGER-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4699: --- Attachment: 0001-RANGER-4699.patch > Update the execution of setServiceDef call in App.jsx > - > > Key: RANGER-4699 > URL: https://issues.apache.org/jira/browse/RANGER-4699 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger >Reporter: Mugdha Varadkar >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4699.patch > > > Need minor code update in executing the setServiceDef() call in App.jsx -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4694) Best coding practices for Audit Admin log tab.
[ https://issues.apache.org/jira/browse/RANGER-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4694: --- Summary: Best coding practices for Audit Admin log tab. (was: Improvement in Audit admin log tab.) > Best coding practices for Audit Admin log tab. > -- > > Key: RANGER-4694 > URL: https://issues.apache.org/jira/browse/RANGER-4694 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Minor > > In current ranger react UI, Improvement in code for Audit Admin log tab. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4694) Improvement in Audit admin log tab.
Dhaval Rajpara created RANGER-4694: -- Summary: Improvement in Audit admin log tab. Key: RANGER-4694 URL: https://issues.apache.org/jira/browse/RANGER-4694 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara In current ranger react UI, Improvement in code for Audit Admin log tab. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4544) Implement best coding practices for policy resources
[ https://issues.apache.org/jira/browse/RANGER-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812254#comment-17812254 ] Dhaval Rajpara commented on RANGER-4544: Patch Committed to [Apache master|https://github.com/apache/ranger/commit/4a621c2a0e450790a43248f04d1ca68028530a3e] branch. > Implement best coding practices for policy resources > > > Key: RANGER-4544 > URL: https://issues.apache.org/jira/browse/RANGER-4544 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: > 0001-RANGER-4544-Implement-best-coding-practices-for-poli.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4544) Implement best coding practices for policy resources
[ https://issues.apache.org/jira/browse/RANGER-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4544: --- Fix Version/s: 3.0.0 > Implement best coding practices for policy resources > > > Key: RANGER-4544 > URL: https://issues.apache.org/jira/browse/RANGER-4544 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4544-Implement-best-coding-practices-for-poli.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4673) Pagination on the Ranger Admin - Plugin Status page
[ https://issues.apache.org/jira/browse/RANGER-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4673: --- Description: The Ranger Admin UI's "Plugin Status" page does not offer pagination. The UI shows only (the first random) 200 entries, we have no way to go to next pages, and the ordering/sorting on columns is only a "client side" sorting so some entries cannot be seen easily. (only if we search by Host Name for example) This is a usability issue with bigger clusters. was: The Ranger Admin UI's "Plugin Status" page does not offer pagination. The UI shows only (the first? random?) 200 entries, we have no way to go to next pages, and the ordering/sorting on columns is only a "client side" sorting so some entries cannot be seen easily. (only if we search by Host Name for example) This is a usability issue with bigger clusters. > Pagination on the Ranger Admin - Plugin Status page > --- > > Key: RANGER-4673 > URL: https://issues.apache.org/jira/browse/RANGER-4673 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > The Ranger Admin UI's "Plugin Status" page does not offer pagination. > The UI shows only (the first random) 200 entries, we have no way to go to > next pages, and the ordering/sorting on columns is only a "client side" > sorting so some entries cannot be seen easily. (only if we search by Host > Name for example) > This is a usability issue with bigger clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4673) Pagination on the Ranger Admin - Plugin Status page
[ https://issues.apache.org/jira/browse/RANGER-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810902#comment-17810902 ] Dhaval Rajpara commented on RANGER-4673: Hi [~madhan], We have created a jira - [RANGER-4673|https://issues.apache.org/jira/browse/RANGER-4673], for a customer where they are facing problem while loading plugin status tab data on there bigger cluster which is having records more than 200. Therefore to resolve the this issue we are thinking of below : 1) For Plugin status tab, currently we are using client side fetching and sorting which we be removed and add a pagination same as used in other tables. 2) From server-side, curently the sorting is only available for "service name" "hostName" and "appType" colums. After we add a pagination on plugin status tab, the client side sorting will be removed and sorting will only be available on the columns supported from server-side. CC : [~dineshkumar-yadav] / [~vel] /[~mehul] / [~mugdha.varadkar] > Pagination on the Ranger Admin - Plugin Status page > --- > > Key: RANGER-4673 > URL: https://issues.apache.org/jira/browse/RANGER-4673 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > The Ranger Admin UI's "Plugin Status" page does not offer pagination. > The UI shows only (the first? random?) 200 entries, we have no way to go to > next pages, and the ordering/sorting on columns is only a "client side" > sorting so some entries cannot be seen easily. (only if we search by Host > Name for example) > This is a usability issue with bigger clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4673) Pagination on the Ranger Admin - Plugin Status page
Dhaval Rajpara created RANGER-4673: -- Summary: Pagination on the Ranger Admin - Plugin Status page Key: RANGER-4673 URL: https://issues.apache.org/jira/browse/RANGER-4673 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara The Ranger Admin UI's "Plugin Status" page does not offer pagination. The UI shows only (the first? random?) 200 entries, we have no way to go to next pages, and the ordering/sorting on columns is only a "client side" sorting so some entries cannot be seen easily. (only if we search by Host Name for example) This is a usability issue with bigger clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4544) Implement best coding practices for policy resources
[ https://issues.apache.org/jira/browse/RANGER-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4544: --- Attachment: 0001-RANGER-4544-Implement-best-coding-practices-for-poli.patch > Implement best coding practices for policy resources > > > Key: RANGER-4544 > URL: https://issues.apache.org/jira/browse/RANGER-4544 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: > 0001-RANGER-4544-Implement-best-coding-practices-for-poli.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4643) Upgrade react-bootstrap library for GDS UI.
Dhaval Rajpara created RANGER-4643: -- Summary: Upgrade react-bootstrap library for GDS UI. Key: RANGER-4643 URL: https://issues.apache.org/jira/browse/RANGER-4643 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4611) Security zone form not populate resources value properly while creating and editing zone.
[ https://issues.apache.org/jira/browse/RANGER-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4611: --- Attachment: 0001-RANGER-4611.patch > Security zone form not populate resources value properly while creating and > editing zone. > - > > Key: RANGER-4611 > URL: https://issues.apache.org/jira/browse/RANGER-4611 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4611.patch > > > Step to Reproduce: > 1) Go to the security zone page. > 2) Click on Create zone button. > 3) Add multiple resources in that time previous value of added resources not > populate properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4502) Getting Error to load backbone.js latest UI.
[ https://issues.apache.org/jira/browse/RANGER-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4502: --- Fix Version/s: 3.0.0 > Getting Error to load backbone.js latest UI. > - > > Key: RANGER-4502 > URL: https://issues.apache.org/jira/browse/RANGER-4502 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4502.patch > > > Step to reproduce: > 1) Login to ranger admin UI > 2) go to the profile drop-down > 3) Click on Switch to latest UI > Result in "NO services found" page displayed. But we have services present in > Backbone Classic UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4502) Getting Error to load backbone.js latest UI.
[ https://issues.apache.org/jira/browse/RANGER-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798593#comment-17798593 ] Dhaval Rajpara commented on RANGER-4502: Code Committed to [Apache Master|https://github.com/apache/ranger/commit/913d737890df43b58ee31de400aa32e9d3d2d08d] branch. > Getting Error to load backbone.js latest UI. > - > > Key: RANGER-4502 > URL: https://issues.apache.org/jira/browse/RANGER-4502 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4502.patch > > > Step to reproduce: > 1) Login to ranger admin UI > 2) go to the profile drop-down > 3) Click on Switch to latest UI > Result in "NO services found" page displayed. But we have services present in > Backbone Classic UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4611) Security zone form not populate resources value properly while creating and editing zone.
[ https://issues.apache.org/jira/browse/RANGER-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4611: --- Summary: Security zone form not populate resources value properly while creating and editing zone. (was: Security zone not populate resources value properly while creating and editing zone.) > Security zone form not populate resources value properly while creating and > editing zone. > - > > Key: RANGER-4611 > URL: https://issues.apache.org/jira/browse/RANGER-4611 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > Step to Reproduce: > 1) Go to the security zone page. > 2) Click on Create zone button. > 3) Add multiple resources in that time previous value of added resources not > populate properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4611) Security zone not populate resources value properly while creating and editing zone.
Dhaval Rajpara created RANGER-4611: -- Summary: Security zone not populate resources value properly while creating and editing zone. Key: RANGER-4611 URL: https://issues.apache.org/jira/browse/RANGER-4611 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Step to Reproduce: 1) Go to the security zone page. 2) Click on Create zone button. 3) Add multiple resources in that time previous value of added resources not populate properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4593) Upgrade react-bootstrap library
Dhaval Rajpara created RANGER-4593: -- Summary: Upgrade react-bootstrap library Key: RANGER-4593 URL: https://issues.apache.org/jira/browse/RANGER-4593 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Upgrade react-bootstrap library version 1.6.7 to 2.9.1. This changes also required bootstrap library Upgrade. so we migrate Bootstrap version 4.6.0 to 5.3.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4502) Getting Error to load backbone.js latest UI.
[ https://issues.apache.org/jira/browse/RANGER-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4502: --- Attachment: 0001-RANGER-4502.patch > Getting Error to load backbone.js latest UI. > - > > Key: RANGER-4502 > URL: https://issues.apache.org/jira/browse/RANGER-4502 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4502.patch > > > Step to reproduce: > 1) Login to ranger admin UI > 2) go to the profile drop-down > 3) Click on Switch to latest UI > Result in "NO services found" page displayed. But we have services present in > Backbone Classic UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4347) User name with comma split in old Ranger admin UI
[ https://issues.apache.org/jira/browse/RANGER-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4347: --- Attachment: 0001-RANGER-4347-User-name-with-comma-split-in-old-Ranger.patch > User name with comma split in old Ranger admin UI > - > > Key: RANGER-4347 > URL: https://issues.apache.org/jira/browse/RANGER-4347 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: > 0001-RANGER-4347-User-name-with-comma-split-in-old-Ranger.patch > > > when using Ranger Audit filter to filter out the audit for a specific user: > Usually, if we input a username, it would be no issue, but if we input the > user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”. > We found that once we saved the audit filter policy, the user was split into > “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com” > It happens because Ranger UI recognize “,” to be separate items. > Same scenario is present in : > 1) Security Zone Form > 2) Permission modules > 3) Role Form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4544) Implement best coding practices for policy resources
Dhaval Rajpara created RANGER-4544: -- Summary: Implement best coding practices for policy resources Key: RANGER-4544 URL: https://issues.apache.org/jira/browse/RANGER-4544 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (RANGER-4010) Update policy UI to support multiple resource-sets for react ranger.
[ https://issues.apache.org/jira/browse/RANGER-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reopened RANGER-4010: Needed Addendum patch for missing changes https://reviews.apache.org/r/74751/ > Update policy UI to support multiple resource-sets for react ranger. > > > Key: RANGER-4010 > URL: https://issues.apache.org/jira/browse/RANGER-4010 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4010.patch > > > 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 the existing UI for > RangerPolicy.resources and having 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] [Resolved] (RANGER-4360) Error page 'Go back' button not redirecting to the right page
[ https://issues.apache.org/jira/browse/RANGER-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara resolved RANGER-4360. Fix Version/s: 3.0.0 Resolution: Fixed > Error page 'Go back' button not redirecting to the right page > -- > > Key: RANGER-4360 > URL: https://issues.apache.org/jira/browse/RANGER-4360 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4360.patch > > > On error page Go back button not work properly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4318) Switching between keymanager and audits pages with idle time in between causes delays in loading page
[ https://issues.apache.org/jira/browse/RANGER-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara resolved RANGER-4318. Resolution: Fixed > Switching between keymanager and audits pages with idle time in between > causes delays in loading page > - > > Key: RANGER-4318 > URL: https://issues.apache.org/jira/browse/RANGER-4318 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > Scenario: > Logged in to ranger admin UI as keyadmin user > Switch to UI with react and lefthand side tab changes > Click on keymanager. Wait for page to load. > Wait for few minutes. > Click on Audits page. Wait for page to load. > Observed that the switch between pages take less time if there is no idle > time in between. > With idle time it takes between 7-12 secs for page to load with just 1 or 2 > keys and very less no of audits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4318) Switching between keymanager and audits pages with idle time in between causes delays in loading page
[ https://issues.apache.org/jira/browse/RANGER-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784010#comment-17784010 ] Dhaval Rajpara commented on RANGER-4318: This is is getting handled in [RANGER-4331|https://issues.apache.org/jira/browse/RANGER-4331] along with the regression. > Switching between keymanager and audits pages with idle time in between > causes delays in loading page > - > > Key: RANGER-4318 > URL: https://issues.apache.org/jira/browse/RANGER-4318 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > Scenario: > Logged in to ranger admin UI as keyadmin user > Switch to UI with react and lefthand side tab changes > Click on keymanager. Wait for page to load. > Wait for few minutes. > Click on Audits page. Wait for page to load. > Observed that the switch between pages take less time if there is no idle > time in between. > With idle time it takes between 7-12 secs for page to load with just 1 or 2 > keys and very less no of audits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4502) Getting Error to load backbone.js latest UI.
Dhaval Rajpara created RANGER-4502: -- Summary: Getting Error to load backbone.js latest UI. Key: RANGER-4502 URL: https://issues.apache.org/jira/browse/RANGER-4502 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Step to reproduce: 1) Login to ranger admin UI 2) go to the profile drop-down 3) Click on Switch to latest UI Result in "NO services found" page displayed. But we have services present in Backbone Classic UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4360) Error page 'Go back' button not redirecting to the right page
[ https://issues.apache.org/jira/browse/RANGER-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4360: --- Attachment: 0001-RANGER-4360.patch > Error page 'Go back' button not redirecting to the right page > -- > > Key: RANGER-4360 > URL: https://issues.apache.org/jira/browse/RANGER-4360 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4360.patch > > > On error page Go back button not work properly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4360) On error page Go back button not work properly
[ https://issues.apache.org/jira/browse/RANGER-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reassigned RANGER-4360: -- Assignee: Dhaval Rajpara > On error page Go back button not work properly > -- > > Key: RANGER-4360 > URL: https://issues.apache.org/jira/browse/RANGER-4360 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Dhaval Rajpara >Priority: Major > > On error page Go back button not work properly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4360) Error page 'Go back' button not redirecting to the right page
[ https://issues.apache.org/jira/browse/RANGER-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4360: --- Summary: Error page 'Go back' button not redirecting to the right page (was: On error page Go back button not work properly) > Error page 'Go back' button not redirecting to the right page > -- > > Key: RANGER-4360 > URL: https://issues.apache.org/jira/browse/RANGER-4360 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Dhaval Rajpara >Priority: Major > > On error page Go back button not work properly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4479) Logs for admin and auditor roles for security zone is not capture in Audit Admin Tab.
[ https://issues.apache.org/jira/browse/RANGER-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara resolved RANGER-4479. Fix Version/s: 3.0.0 Resolution: Fixed > Logs for admin and auditor roles for security zone is not capture in Audit > Admin Tab. > - > > Key: RANGER-4479 > URL: https://issues.apache.org/jira/browse/RANGER-4479 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0 > > > Added admin and auditor roles in a security zone in Jira > [RANGER-4274|https://issues.apache.org/jira/browse/RANGER-4274]. But the > related Audit admin log Update / delete / Create zone with roles log not > captured in the Admin tab. > CC : [~madhan] / [~pradeep] / [~mehul] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4280) Update security-zone UI with addition of admin-roles and audit-roles
[ https://issues.apache.org/jira/browse/RANGER-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4280: --- Attachment: 0001-RANGER-4280.patch > Update security-zone UI with addition of admin-roles and audit-roles > > > Key: RANGER-4280 > URL: https://issues.apache.org/jira/browse/RANGER-4280 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Madhan Neethiraj >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4280.patch > > > RANGER-4274 added enhancements in security-zone with addition of admin-roles > and audit-roles. UI should be updated for the same. > CC: [~ni3galave], [~Dhaval.Rajpara] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4479) Logs for admin and auditor roles for security zone is not capture in Audit Admin Tab.
[ https://issues.apache.org/jira/browse/RANGER-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1573#comment-1573 ] Dhaval Rajpara commented on RANGER-4479: Hi [~madhan] Yes sure i will add this changes to [RANGER-4280|https://issues.apache.org/jira/browse/RANGER-4280] patch. Thanks > Logs for admin and auditor roles for security zone is not capture in Audit > Admin Tab. > - > > Key: RANGER-4479 > URL: https://issues.apache.org/jira/browse/RANGER-4479 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > Added admin and auditor roles in a security zone in Jira > [RANGER-4274|https://issues.apache.org/jira/browse/RANGER-4274]. But the > related Audit admin log Update / delete / Create zone with roles log not > captured in the Admin tab. > CC : [~madhan] / [~pradeep] / [~mehul] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4479) Logs for admin and auditor roles for security zone is not capture in Audit Admin Tab.
[ https://issues.apache.org/jira/browse/RANGER-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4479: --- Description: Added admin and auditor roles in a security zone in Jira [RANGER-4274|https://issues.apache.org/jira/browse/RANGER-4274]. But the related Audit admin log Update / delete / Create zone with roles log not captured in the Admin tab. CC : [~madhan] / [~pradeep] / [~mehul] was:Added admin and auditor roles in a security zone in Jira [RANGER-4274|https://issues.apache.org/jira/browse/RANGER-4274]. But the related Audit admin log Update / delete / Create zone with roles log not captured in the Admin tab. > Logs for admin and auditor roles for security zone is not capture in Audit > Admin Tab. > - > > Key: RANGER-4479 > URL: https://issues.apache.org/jira/browse/RANGER-4479 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > Added admin and auditor roles in a security zone in Jira > [RANGER-4274|https://issues.apache.org/jira/browse/RANGER-4274]. But the > related Audit admin log Update / delete / Create zone with roles log not > captured in the Admin tab. > CC : [~madhan] / [~pradeep] / [~mehul] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4479) Logs for admin and auditor roles for security zone is not capture in Audit Admin Tab.
Dhaval Rajpara created RANGER-4479: -- Summary: Logs for admin and auditor roles for security zone is not capture in Audit Admin Tab. Key: RANGER-4479 URL: https://issues.apache.org/jira/browse/RANGER-4479 Project: Ranger Issue Type: New Feature Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Added admin and auditor roles in a security zone in Jira [RANGER-4274|https://issues.apache.org/jira/browse/RANGER-4274]. But the related Audit admin log Update / delete / Create zone with roles log not captured in the Admin tab. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4461) Implement best coding practices for validating user input
[ https://issues.apache.org/jira/browse/RANGER-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4461: --- Attachment: 0001-RANGER-4461.patch > Implement best coding practices for validating user input > -- > > Key: RANGER-4461 > URL: https://issues.apache.org/jira/browse/RANGER-4461 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4461.patch > > > Implement best coding practices for validating user input -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4461) Implement best coding practices for validating user input
Dhaval Rajpara created RANGER-4461: -- Summary: Implement best coding practices for validating user input Key: RANGER-4461 URL: https://issues.apache.org/jira/browse/RANGER-4461 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Implement best coding practices for validating user input -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4450) Inconsistencies in API (service/plugins/definitions) response when user has insufficient permissions.
Dhaval Rajpara created RANGER-4450: -- Summary: Inconsistencies in API (service/plugins/definitions) response when user has insufficient permissions. Key: RANGER-4450 URL: https://issues.apache.org/jira/browse/RANGER-4450 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Dhaval Rajpara API : *service/plugins/definitions* This API provides extensive information on service definitions(Resource base Policies module and tag base Policies module) in JSON format. Case 1 : 1) Remove user permission from the resources base module and only allow tag base module permission to that user. 2) Login with that user. This API retunes 403 forbidden for that user. 3) However the same user can get resource base policy definition information through Name and ID For example: service/plugins/definitions/name/hdfs, service/plugins/definitions/name/hbase Any reason why we restrict this API (service/plugins/definitions) for user roles? We want this API open for optimization performance in Ranger React UI. CC : [~madhan] / [~abhay] / [~pradeep] / [~dineshkumar-yadav] /[~mehul] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4010) Update policy UI to support multiple resource-sets for react ranger.
[ https://issues.apache.org/jira/browse/RANGER-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4010: --- Attachment: 0001-RANGER-4010.patch > Update policy UI to support multiple resource-sets for react ranger. > > > Key: RANGER-4010 > URL: https://issues.apache.org/jira/browse/RANGER-4010 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4010.patch > > > 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 the existing UI for > RangerPolicy.resources and having 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-4419) In Tag-based policy from Ranger Admin UI, Allow Conditions permissions item is not showing services permissions which have enableDenyAndExceptionsInPolicies flag false.
[ https://issues.apache.org/jira/browse/RANGER-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4419: --- Attachment: 0001-RANGER-4419.patch > In Tag-based policy from Ranger Admin UI, Allow Conditions permissions item > is not showing services permissions which have > enableDenyAndExceptionsInPolicies flag false. > > > Key: RANGER-4419 > URL: https://issues.apache.org/jira/browse/RANGER-4419 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Attachments: 0001-RANGER-4419.patch > > > Step to reproduce : > 1) Click on Create tag base policy button. > 2) Go to Allow conditions --> Component Permissions > 3) Click on Component Permissions + icon > 4) In Component Permissions modal Select component, it is not showing > component(services) which has flag "enableDenyAndExceptionsInPolicies = false" > The following service components have the option > "enableDenyAndExceptionsInPolicies=false" in service definition. > * elasticsearch > * kylin > * nifi-registry > * nifi > * sqoop > However, these service components should be shown in the Allow condition. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4419) In Tag-based policy from Ranger Admin UI, Allow Conditions permissions item is not showing services permissions which have enableDenyAndExceptionsInPolicies flag false.
Dhaval Rajpara created RANGER-4419: -- Summary: In Tag-based policy from Ranger Admin UI, Allow Conditions permissions item is not showing services permissions which have enableDenyAndExceptionsInPolicies flag false. Key: RANGER-4419 URL: https://issues.apache.org/jira/browse/RANGER-4419 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Step to reproduce : 1) Click on Create tag base policy button. 2) Go to Allow conditions --> Component Permissions 3) Click on Component Permissions + icon 4) In Component Permissions modal Select component, it is not showing component(services) which has flag "enableDenyAndExceptionsInPolicies = false" The following service components have the option "enableDenyAndExceptionsInPolicies=false" in service definition. * elasticsearch * kylin * nifi-registry * nifi * sqoop However, these service components should be shown in the Allow condition. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4368) Audit filter in Tag base service display wrong value for resources
[ https://issues.apache.org/jira/browse/RANGER-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4368: --- Attachment: 0001-RANGER-4368.patch > Audit filter in Tag base service display wrong value for resources > -- > > Key: RANGER-4368 > URL: https://issues.apache.org/jira/browse/RANGER-4368 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4368.patch > > > Step > 1) Click on Add service for tag base policy. > 2) Click on add resources in the Audit filter. > 3) Enter the value and save the resources. > 4) That time Enter a value for that resource not displayed properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4347) User name with comma split in old Ranger admin UI
[ https://issues.apache.org/jira/browse/RANGER-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4347: --- Summary: User name with comma split in old Ranger admin UI (was: User name with comma spited in old Ranger admin UI .) > User name with comma split in old Ranger admin UI > - > > Key: RANGER-4347 > URL: https://issues.apache.org/jira/browse/RANGER-4347 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > when using Ranger Audit filter to filter out the audit for a specific user: > Usually, if we input a username, it would be no issue, but if we input the > user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”. > We found that once we saved the audit filter policy, the user was split into > “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com” > It happens because Ranger UI recognize “,” to be separate items. > Same scenario is present in : > 1) Security Zone Form > 2) Permission modules > 3) Role Form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4119) [UI] Syntax check button missing in policy level condition
[
https://issues.apache.org/jira/browse/RANGER-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhaval Rajpara updated RANGER-4119:
---
Attachment: 0001-RANGER-4119-Improvement-in-policy-condition-on-Range.patch
> [UI] Syntax check button missing in policy level condition
> --
>
> Key: RANGER-4119
> URL: https://issues.apache.org/jira/browse/RANGER-4119
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.4.0
>Reporter: Madhan Neethiraj
>Assignee: Dhaval Rajpara
>Priority: Major
> Labels: ranger-react
> Attachments:
> 0001-RANGER-4119-Improvement-in-policy-condition-on-Range.patch,
> image-2023-03-03-00-04-10-367.png, image-2023-03-03-00-04-45-845.png
>
>
> Ranger policy UI provides {{Syntax check}} button that allows policy authors
> to check if condition expression entered is valid or not. This button is
> available for condition in policy-item level, but its not available for
> condition at policy level - as seen in following images:
>
> Policy-item level:
> !image-2023-03-03-00-04-45-845.png|width=661,height=453!
>
> Policy level:
> !image-2023-03-03-00-04-10-367.png|width=661,height=488!
>
> CC: [~ni3galave], [~Dhaval.Rajpara]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4119) [UI] Syntax check button missing in policy level condition
[
https://issues.apache.org/jira/browse/RANGER-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757301#comment-17757301
]
Dhaval Rajpara commented on RANGER-4119:
Hi [~madhan],
Regarding this, we added fixes only in react.js UI.
In the new react.js UI, we provided run time validation. we removed the Syntax
check button.
The error is displayed when the user enters a value in the expression column.
Thanks,
Dhaval
> [UI] Syntax check button missing in policy level condition
> --
>
> Key: RANGER-4119
> URL: https://issues.apache.org/jira/browse/RANGER-4119
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.4.0
>Reporter: Madhan Neethiraj
>Assignee: Dhaval Rajpara
>Priority: Major
> Labels: ranger-react
> Attachments: image-2023-03-03-00-04-10-367.png,
> image-2023-03-03-00-04-45-845.png
>
>
> Ranger policy UI provides {{Syntax check}} button that allows policy authors
> to check if condition expression entered is valid or not. This button is
> available for condition in policy-item level, but its not available for
> condition at policy level - as seen in following images:
>
> Policy-item level:
> !image-2023-03-03-00-04-45-845.png|width=661,height=453!
>
> Policy level:
> !image-2023-03-03-00-04-10-367.png|width=661,height=488!
>
> CC: [~ni3galave], [~Dhaval.Rajpara]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4368) Audit filter in Tag base service display wrong value for resources
Dhaval Rajpara created RANGER-4368: -- Summary: Audit filter in Tag base service display wrong value for resources Key: RANGER-4368 URL: https://issues.apache.org/jira/browse/RANGER-4368 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Step 1) Click on Add service for tag base policy. 2) Click on add resources in the Audit filter. 3) Enter the value and save the resources. 4) That time Enter a value for that resource not displayed properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4347) User name with comma spited in old Ranger admin UI .
[ https://issues.apache.org/jira/browse/RANGER-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4347: --- Summary: User name with comma spited in old Ranger admin UI . (was: User name with "," spited in old Ranger admin UI .) > User name with comma spited in old Ranger admin UI . > > > Key: RANGER-4347 > URL: https://issues.apache.org/jira/browse/RANGER-4347 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > when using Ranger Audit filter to filter out the audit for a specific user: > Usually, if we input a username, it would be no issue, but if we input the > user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”. > We found that once we saved the audit filter policy, the user was split into > “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com” > It happens because Ranger UI recognize “,” to be separate items. > Same scenario is present in : > 1) Security Zone Form > 2) Permission modules > 3) Role Form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4347) User name with "," spited in old Ranger admin UI .
Dhaval Rajpara created RANGER-4347: -- Summary: User name with "," spited in old Ranger admin UI . Key: RANGER-4347 URL: https://issues.apache.org/jira/browse/RANGER-4347 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara when using Ranger Audit filter to filter out the audit for a specific user: Usually, if we input a username, it would be no issue, but if we input the user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”. We found that once we saved the audit filter policy, the user was split into “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com” It happens because Ranger UI recognize “,” to be separate items. Same scenario is present in : 1) Security Zone Form 2) Permission modules 3) Role Form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4318) Switching between keymanager and audits pages with idle time in between causes delays in loading page
[ https://issues.apache.org/jira/browse/RANGER-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4318: --- Labels: ranger-react (was: ) > Switching between keymanager and audits pages with idle time in between > causes delays in loading page > - > > Key: RANGER-4318 > URL: https://issues.apache.org/jira/browse/RANGER-4318 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > Scenario: > Logged in to ranger admin UI as keyadmin user > Switch to UI with react and lefthand side tab changes > Click on keymanager. Wait for page to load. > Wait for few minutes. > Click on Audits page. Wait for page to load. > Observed that the switch between pages take less time if there is no idle > time in between. > With idle time it takes between 7-12 secs for page to load with just 1 or 2 > keys and very less no of audits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4318) Switching between keymanager and audits pages with idle time in between causes delays in loading page
Dhaval Rajpara created RANGER-4318: -- Summary: Switching between keymanager and audits pages with idle time in between causes delays in loading page Key: RANGER-4318 URL: https://issues.apache.org/jira/browse/RANGER-4318 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Scenario: Logged in to ranger admin UI as keyadmin user Switch to UI with react and lefthand side tab changes Click on keymanager. Wait for page to load. Wait for few minutes. Click on Audits page. Wait for page to load. Observed that the switch between pages take less time if there is no idle time in between. With idle time it takes between 7-12 secs for page to load with just 1 or 2 keys and very less no of audits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4317) Ranger React : Error message displayed when resource lookup fails is not formatted properly
Dhaval Rajpara created RANGER-4317: -- Summary: Ranger React : Error message displayed when resource lookup fails is not formatted properly Key: RANGER-4317 URL: https://issues.apache.org/jira/browse/RANGER-4317 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Brijesh Bhalala When a resource lookup fails on the new UI due to some config issue, the error message is not displayed properly But on backbone JS, it is displayed properly. The error message on react js must be formatted properly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4294) Delete message alert box should have message specific to delete activity
[ https://issues.apache.org/jira/browse/RANGER-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4294: --- Fix Version/s: 3.0.0 > Delete message alert box should have message specific to delete activity > > > Key: RANGER-4294 > URL: https://issues.apache.org/jira/browse/RANGER-4294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4294.patch > > > Delete message alert box should have message specific to delete activity. > Try to delete service - Observe - Delete message alert box > Try to delete policy - Observe - Delete message alert box > Both Delete message alert box on same page , no specific details about which > operation is performed > Earlier in backbone Js both deletion happens of different page . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4280) Update security-zone UI with addition of admin-roles and audit-roles
[ https://issues.apache.org/jira/browse/RANGER-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reassigned RANGER-4280: -- Assignee: Dhaval Rajpara > Update security-zone UI with addition of admin-roles and audit-roles > > > Key: RANGER-4280 > URL: https://issues.apache.org/jira/browse/RANGER-4280 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Madhan Neethiraj >Assignee: Dhaval Rajpara >Priority: Major > > RANGER-4274 added enhancements in security-zone with addition of admin-roles > and audit-roles. UI should be updated for the same. > CC: [~ni3galave], [~Dhaval.Rajpara] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4263) LookupResource give blank response in new react UI
[
https://issues.apache.org/jira/browse/RANGER-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhaval Rajpara updated RANGER-4263:
---
Attachment: Ranger_Policies_20230621_093238.xls
> LookupResource give blank response in new react UI
> --
>
> Key: RANGER-4263
> URL: https://issues.apache.org/jira/browse/RANGER-4263
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Dhaval Rajpara
>Priority: Major
> Labels: ranger-react
> Attachments: 0001-RANGER-4263.patch,
> Ranger_Policies_20230621_093238.xls
>
>
> Ranger] : plugins/services/lookupResource give bank response in react API
> New react ui hit below api
> [https://***2/service/plugins/services/lookupResource/cm_solr|https://quasar-wqeuts-1.quasar-wqeuts.root.hwx.site:6182/service/plugins/services/lookupResource/cm_solr]
> request data : without userInput
> {code:java}
> {"resourceName":"collection","resources":{"collection":[]}}{code}
> response :
> {code:java}
> 204 = no content {code}
> Ideally default resouce should be loaded and below request should be passed
> by click action
> {"userInput": "","resourceName":"collection","resources":\{"collection":[]}}
> Expected : Default resouces should be lookup , If user clicks on dropdown or
> on text field
> 2) Add a loader to select 2 options while changing the resource field.
> 3) If the service definition of resources has singleValue : true then the
> user is not able to select more than one value.
> 4) if we enter * in resource value then it will load all the options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4263) LookupResource give blank response in new react UI
[
https://issues.apache.org/jira/browse/RANGER-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhaval Rajpara updated RANGER-4263:
---
Attachment: 0001-RANGER-4263.patch
> LookupResource give blank response in new react UI
> --
>
> Key: RANGER-4263
> URL: https://issues.apache.org/jira/browse/RANGER-4263
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Dhaval Rajpara
>Priority: Major
> Labels: ranger-react
> Attachments: 0001-RANGER-4263.patch
>
>
> Ranger] : plugins/services/lookupResource give bank response in react API
> New react ui hit below api
> [https://***2/service/plugins/services/lookupResource/cm_solr|https://quasar-wqeuts-1.quasar-wqeuts.root.hwx.site:6182/service/plugins/services/lookupResource/cm_solr]
> request data : without userInput
> {code:java}
> {"resourceName":"collection","resources":{"collection":[]}}{code}
> response :
> {code:java}
> 204 = no content {code}
> Ideally default resouce should be loaded and below request should be passed
> by click action
> {"userInput": "","resourceName":"collection","resources":\{"collection":[]}}
> Expected : Default resouces should be lookup , If user clicks on dropdown or
> on text field
> 2) Add a loader to select 2 options while changing the resource field.
> 3) If the service definition of resources has singleValue : true then the
> user is not able to select more than one value.
> 4) if we enter * in resource value then it will load all the options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4294) Delete message alert box should have message specific to delete activity
[ https://issues.apache.org/jira/browse/RANGER-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4294: --- Attachment: (was: 0001-RABGER-4294.patch) > Delete message alert box should have message specific to delete activity > > > Key: RANGER-4294 > URL: https://issues.apache.org/jira/browse/RANGER-4294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4294.patch > > > Delete message alert box should have message specific to delete activity. > Try to delete service - Observe - Delete message alert box > Try to delete policy - Observe - Delete message alert box > Both Delete message alert box on same page , no specific details about which > operation is performed > Earlier in backbone Js both deletion happens of different page . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4294) Delete message alert box should have message specific to delete activity
[ https://issues.apache.org/jira/browse/RANGER-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4294: --- Attachment: 0001-RANGER-4294.patch > Delete message alert box should have message specific to delete activity > > > Key: RANGER-4294 > URL: https://issues.apache.org/jira/browse/RANGER-4294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4294.patch > > > Delete message alert box should have message specific to delete activity. > Try to delete service - Observe - Delete message alert box > Try to delete policy - Observe - Delete message alert box > Both Delete message alert box on same page , no specific details about which > operation is performed > Earlier in backbone Js both deletion happens of different page . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4294) Delete message alert box should have message specific to delete activity
[ https://issues.apache.org/jira/browse/RANGER-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4294: --- Attachment: 0001-RABGER-4294.patch > Delete message alert box should have message specific to delete activity > > > Key: RANGER-4294 > URL: https://issues.apache.org/jira/browse/RANGER-4294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RABGER-4294.patch > > > Delete message alert box should have message specific to delete activity. > Try to delete service - Observe - Delete message alert box > Try to delete policy - Observe - Delete message alert box > Both Delete message alert box on same page , no specific details about which > operation is performed > Earlier in backbone Js both deletion happens of different page . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4263) LookupResource give blank response in new react UI
[
https://issues.apache.org/jira/browse/RANGER-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhaval Rajpara updated RANGER-4263:
---
Description:
Ranger] : plugins/services/lookupResource give bank response in react API
New react ui hit below api
[https://***2/service/plugins/services/lookupResource/cm_solr|https://quasar-wqeuts-1.quasar-wqeuts.root.hwx.site:6182/service/plugins/services/lookupResource/cm_solr]
request data : without userInput
{code:java}
{"resourceName":"collection","resources":{"collection":[]}}{code}
response :
{code:java}
204 = no content {code}
Ideally default resouce should be loaded and below request should be passed by
click action
{"userInput": "","resourceName":"collection","resources":\{"collection":[]}}
Expected : Default resouces should be lookup , If user clicks on dropdown or on
text field
2) Add a loader to select 2 options while changing the resource field.
3) If the service definition of resources has singleValue : true then the user
is not able to select more than one value.
4) if we enter * in resource value then it will load all the options.
was:
Ranger] : plugins/services/lookupResource give bank response in react API
New react ui hit below api
[https://***2/service/plugins/services/lookupResource/cm_solr|https://quasar-wqeuts-1.quasar-wqeuts.root.hwx.site:6182/service/plugins/services/lookupResource/cm_solr]
request data : without userInput
{code:java}
{"resourceName":"collection","resources":{"collection":[]}}{code}
response :
{code:java}
204 = no content {code}
Ideally default resouce should be loaded and below request should be passed by
click action
{"userInput": "","resourceName":"collection","resources":\{"collection":[]}}
Expected : Default resouces should be lookup , If user clicks on dropdown or on
text field
> LookupResource give blank response in new react UI
> --
>
> Key: RANGER-4263
> URL: https://issues.apache.org/jira/browse/RANGER-4263
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Dhaval Rajpara
>Priority: Major
> Labels: ranger-react
>
> Ranger] : plugins/services/lookupResource give bank response in react API
> New react ui hit below api
> [https://***2/service/plugins/services/lookupResource/cm_solr|https://quasar-wqeuts-1.quasar-wqeuts.root.hwx.site:6182/service/plugins/services/lookupResource/cm_solr]
> request data : without userInput
> {code:java}
> {"resourceName":"collection","resources":{"collection":[]}}{code}
> response :
> {code:java}
> 204 = no content {code}
> Ideally default resouce should be loaded and below request should be passed
> by click action
> {"userInput": "","resourceName":"collection","resources":\{"collection":[]}}
> Expected : Default resouces should be lookup , If user clicks on dropdown or
> on text field
> 2) Add a loader to select 2 options while changing the resource field.
> 3) If the service definition of resources has singleValue : true then the
> user is not able to select more than one value.
> 4) if we enter * in resource value then it will load all the options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4081) [Ranger UI] [React JS] If the url to edit a policy, service or permissions for a module, and the url to view user/group/roles contains an invalid id, then page should di
[ https://issues.apache.org/jira/browse/RANGER-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4081: --- Fix Version/s: 3.0.0 > [Ranger UI] [React JS] If the url to edit a policy, service or permissions > for a module, and the url to view user/group/roles contains an invalid id, > then page should display an error > --- > > Key: RANGER-4081 > URL: https://issues.apache.org/jira/browse/RANGER-4081 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4081.patch > > > If the url to edit a policy, a service or permissions for a certain module > contains an invalid service id or a policy id, > then the page is stuck in loading state. > Ideally, if the service or a policy for a given id does not exist, then the > page should > display the appropriate error message. > If the url to view the user/group/role details also has an invalid id, the > page is stuck in loading state instead of displaying an error. > For example, if the url to edit a security zone contains an invalid zone id, > there is a popup that displays the message "Data not found for given id". A > similar message should be displayed for other urls with invalid ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4294) Delete message alert box should have message specific to delete activity
[ https://issues.apache.org/jira/browse/RANGER-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reassigned RANGER-4294: -- Assignee: Dhaval Rajpara > Delete message alert box should have message specific to delete activity > > > Key: RANGER-4294 > URL: https://issues.apache.org/jira/browse/RANGER-4294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > Delete message alert box should have message specific to delete activity. > Try to delete service - Observe - Delete message alert box > Try to delete policy - Observe - Delete message alert box > Both Delete message alert box on same page , no specific details about which > operation is performed > Earlier in backbone Js both deletion happens of different page . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4081) [Ranger UI] [React JS] If the url to edit a policy, service or permissions for a module, and the url to view user/group/roles contains an invalid id, then page should di
[ https://issues.apache.org/jira/browse/RANGER-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4081: --- Attachment: 0001-RANGER-4081.patch > [Ranger UI] [React JS] If the url to edit a policy, service or permissions > for a module, and the url to view user/group/roles contains an invalid id, > then page should display an error > --- > > Key: RANGER-4081 > URL: https://issues.apache.org/jira/browse/RANGER-4081 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4081.patch > > > If the url to edit a policy, a service or permissions for a certain module > contains an invalid service id or a policy id, > then the page is stuck in loading state. > Ideally, if the service or a policy for a given id does not exist, then the > page should > display the appropriate error message. > If the url to view the user/group/role details also has an invalid id, the > page is stuck in loading state instead of displaying an error. > For example, if the url to edit a security zone contains an invalid zone id, > there is a popup that displays the message "Data not found for given id". A > similar message should be displayed for other urls with invalid ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4197) Encryption Tab's key manager table show blank data.
[ https://issues.apache.org/jira/browse/RANGER-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4197: --- Fix Version/s: 3.0.0 > Encryption Tab's key manager table show blank data. > --- > > Key: RANGER-4197 > URL: https://issues.apache.org/jira/browse/RANGER-4197 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4197.patch > > > Encryption Tab's key manager table shows blank data in the attributes column. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4081) [Ranger UI] [React JS] If the url to edit a policy, service or permissions for a module, and the url to view user/group/roles contains an invalid id, then page should d
[ https://issues.apache.org/jira/browse/RANGER-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reassigned RANGER-4081: -- Assignee: Dhaval Rajpara (was: Dineshkumar Yadav) > [Ranger UI] [React JS] If the url to edit a policy, service or permissions > for a module, and the url to view user/group/roles contains an invalid id, > then page should display an error > --- > > Key: RANGER-4081 > URL: https://issues.apache.org/jira/browse/RANGER-4081 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > If the url to edit a policy, a service or permissions for a certain module > contains an invalid service id or a policy id, > then the page is stuck in loading state. > Ideally, if the service or a policy for a given id does not exist, then the > page should > display the appropriate error message. > If the url to view the user/group/role details also has an invalid id, the > page is stuck in loading state instead of displaying an error. > For example, if the url to edit a security zone contains an invalid zone id, > there is a popup that displays the message "Data not found for given id". A > similar message should be displayed for other urls with invalid ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4103) [Ranger-react] Fix for improving logout mechanism in Ranger react code base.
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4103: --- Fix Version/s: 3.0.0 (was: 2.4.1) > [Ranger-react] Fix for improving logout mechanism in Ranger react code base. > > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4103.patch > > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4103) [Ranger-react] Fix for improving logout mechanism in Ranger react code base.
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726076#comment-17726076 ] Dhaval Rajpara commented on RANGER-4103: Committed to [Apache master|https://github.com/apache/ranger/commit/21c6e24e6cf5c09cf719e53c737b6409b0bc08aa] branch. > [Ranger-react] Fix for improving logout mechanism in Ranger react code base. > > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 2.4.1 > > Attachments: 0001-RANGER-4103.patch > > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4103) [Ranger-react] Fix for improving logout mechanism in Ranger react code base.
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4103: --- Fix Version/s: 2.4.1 > [Ranger-react] Fix for improving logout mechanism in Ranger react code base. > > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 2.4.1 > > Attachments: 0001-RANGER-4103.patch > > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4223) Policy view pop-up does not render deny-all-else toggle
[ https://issues.apache.org/jira/browse/RANGER-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara reassigned RANGER-4223: -- Assignee: Dhaval Rajpara > Policy view pop-up does not render deny-all-else toggle > --- > > Key: RANGER-4223 > URL: https://issues.apache.org/jira/browse/RANGER-4223 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Madhan Neethiraj >Assignee: Dhaval Rajpara >Priority: Major > Attachments: view-policy.png > > > On clicking view button next to a policy, a pop-up windows is rendered > showing details of the policy, like the one shown in the attached image. This > pop-up does not include the toggle for denyAllElse flag, which is a critical > flag to interpret the impact of the policy. > [~nitin.galave], [~Dhaval.Rajpara] - can you please review? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4103) [Ranger-react] Fix for improving logout mechanism in Ranger react code base.
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4103: --- Attachment: 0001-RANGER-4103.patch > [Ranger-react] Fix for improving logout mechanism in Ranger react code base. > > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4103.patch > > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4103) [Ranger-react] Fix for improving logout mechanism in Ranger react code base.
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4103: --- Summary: [Ranger-react] Fix for improving logout mechanism in Ranger react code base. (was: [Ranger-react] Fix for improving logout mechanism in Ranger react code base) > [Ranger-react] Fix for improving logout mechanism in Ranger react code base. > > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4103) [Ranger-react]Something went wrong page display while log out.
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4103: --- Attachment: (was: 0001-RANGER-4103.patch) > [Ranger-react]Something went wrong page display while log out. > -- > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4103) [Ranger-react] Fix for improving logout mechanism in Ranger react code base
[ https://issues.apache.org/jira/browse/RANGER-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4103: --- Summary: [Ranger-react] Fix for improving logout mechanism in Ranger react code base (was: [Ranger-react]Something went wrong page display while log out.) > [Ranger-react] Fix for improving logout mechanism in Ranger react code base > --- > > Key: RANGER-4103 > URL: https://issues.apache.org/jira/browse/RANGER-4103 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > > While logout to react UI "Something went wrong" Page appear and than login > page come -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4197) Encryption Tab's key manager table show blank data.
[ https://issues.apache.org/jira/browse/RANGER-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4197: --- Attachment: 0001-RANGER-4197.patch > Encryption Tab's key manager table show blank data. > --- > > Key: RANGER-4197 > URL: https://issues.apache.org/jira/browse/RANGER-4197 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4197.patch > > > Encryption Tab's key manager table shows blank data in the attributes column. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4197) Encryption Tab's key manager table show blank data.
Dhaval Rajpara created RANGER-4197: -- Summary: Encryption Tab's key manager table show blank data. Key: RANGER-4197 URL: https://issues.apache.org/jira/browse/RANGER-4197 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 3.0.0 Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara Encryption Tab's key manager table shows blank data in the attributes column. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4087) Loader is still loading for resource field for policy creation even after Resource lookup API gives 200/204
[ https://issues.apache.org/jira/browse/RANGER-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713534#comment-17713534 ] Dhaval Rajpara commented on RANGER-4087: Committed to Apache [master|https://github.com/apache/ranger/commit/12edeb578473686188e884a9422bb876c2babc10] branch. > Loader is still loading for resource field for policy creation even after > Resource lookup API gives 200/204 > --- > > Key: RANGER-4087 > URL: https://issues.apache.org/jira/browse/RANGER-4087 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4087.patch, 0002-RANGER-4087.patch > > > Loader is still loading for resource field for policy creation even after > Resource lookup API gives 200/204 > Steps to reproduce : > 1. Create a hive Policy > 2. Edit that policy > 3. Go back to ranger home page and again navigate back to policy with edit > option > Actual : Resouce fields are still having loader which seems its still > waiting for resouce even Resource lookup API gives 200/204. > Expected : Loader should not be there after some time -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4090) Resouce lookup exception message is not available in react UI
[ https://issues.apache.org/jira/browse/RANGER-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713533#comment-17713533 ] Dhaval Rajpara commented on RANGER-4090: Committed to apache [master|https://github.com/apache/ranger/commit/d3574f886c72e1554ddb6d57969e6a2c09bc9967] branch. > Resouce lookup exception message is not available in react UI > - > > Key: RANGER-4090 > URL: https://issues.apache.org/jira/browse/RANGER-4090 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4090.patch, 0002-RANGER-4090.patch > > > Resouce lookup exception message is not available in react UI > Steps to reproduce : > 1. While creating policy enter any resouce name which is not available > Actual : We are not getting any expception message related to these resouce > while resouce lookup > Expected : Like Old ui user should get these expection message for resource > lookup > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4090) Resouce lookup exception message is not available in react UI
[ https://issues.apache.org/jira/browse/RANGER-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4090: --- Fix Version/s: 3.0.0 > Resouce lookup exception message is not available in react UI > - > > Key: RANGER-4090 > URL: https://issues.apache.org/jira/browse/RANGER-4090 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4090.patch, 0002-RANGER-4090.patch > > > Resouce lookup exception message is not available in react UI > Steps to reproduce : > 1. While creating policy enter any resouce name which is not available > Actual : We are not getting any expception message related to these resouce > while resouce lookup > Expected : Like Old ui user should get these expection message for resource > lookup > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered
[ https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4088: --- Fix Version/s: 3.0.0 > While editing policy All permissions & and other resource fields are getting > disappered > --- > > Key: RANGER-4088 > URL: https://issues.apache.org/jira/browse/RANGER-4088 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Critical > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4088.patch, Screenshot 2023-02-15 at 4.51.18 > PM.png > > > While editing policy All permissions & and other resource fields are getting > disappered. > Steps to reproduce : > 1. Create a hive policy with resource Database , Table , column and give all > permission to user > 2 Try to edit same policy , now select service in resouce and again select > database > 3. Observe that no other resource fields are coming and permission given to > user is also removed. > Expected : User should be able to get all related fields -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered
[ https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713532#comment-17713532 ] Dhaval Rajpara commented on RANGER-4088: Committed changes to the [master|https://github.com/apache/ranger/commit/6d88806d1475395721a33ee834975a8d33bc43d1] branch. > While editing policy All permissions & and other resource fields are getting > disappered > --- > > Key: RANGER-4088 > URL: https://issues.apache.org/jira/browse/RANGER-4088 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Critical > Labels: ranger-react > Attachments: 0001-RANGER-4088.patch, Screenshot 2023-02-15 at 4.51.18 > PM.png > > > While editing policy All permissions & and other resource fields are getting > disappered. > Steps to reproduce : > 1. Create a hive policy with resource Database , Table , column and give all > permission to user > 2 Try to edit same policy , now select service in resouce and again select > database > 3. Observe that no other resource fields are coming and permission given to > user is also removed. > Expected : User should be able to get all related fields -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered
[ https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4088: --- Attachment: 0001-RANGER-4088.patch > While editing policy All permissions & and other resource fields are getting > disappered > --- > > Key: RANGER-4088 > URL: https://issues.apache.org/jira/browse/RANGER-4088 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Critical > Labels: ranger-react > Attachments: 0001-RANGER-4088.patch, Screenshot 2023-02-15 at 4.51.18 > PM.png > > > While editing policy All permissions & and other resource fields are getting > disappered. > Steps to reproduce : > 1. Create a hive policy with resource Database , Table , column and give all > permission to user > 2 Try to edit same policy , now select service in resouce and again select > database > 3. Observe that no other resource fields are coming and permission given to > user is also removed. > Expected : User should be able to get all related fields -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered
[ https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4088: --- Attachment: (was: 0003-RANGER-4090.patch) > While editing policy All permissions & and other resource fields are getting > disappered > --- > > Key: RANGER-4088 > URL: https://issues.apache.org/jira/browse/RANGER-4088 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Critical > Labels: ranger-react > Attachments: Screenshot 2023-02-15 at 4.51.18 PM.png > > > While editing policy All permissions & and other resource fields are getting > disappered. > Steps to reproduce : > 1. Create a hive policy with resource Database , Table , column and give all > permission to user > 2 Try to edit same policy , now select service in resouce and again select > database > 3. Observe that no other resource fields are coming and permission given to > user is also removed. > Expected : User should be able to get all related fields -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered
[ https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4088: --- Attachment: 0003-RANGER-4090.patch > While editing policy All permissions & and other resource fields are getting > disappered > --- > > Key: RANGER-4088 > URL: https://issues.apache.org/jira/browse/RANGER-4088 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Critical > Labels: ranger-react > Attachments: Screenshot 2023-02-15 at 4.51.18 PM.png > > > While editing policy All permissions & and other resource fields are getting > disappered. > Steps to reproduce : > 1. Create a hive policy with resource Database , Table , column and give all > permission to user > 2 Try to edit same policy , now select service in resouce and again select > database > 3. Observe that no other resource fields are coming and permission given to > user is also removed. > Expected : User should be able to get all related fields -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4090) Resouce lookup exception message is not available in react UI
[ https://issues.apache.org/jira/browse/RANGER-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4090: --- Attachment: 0002-RANGER-4090.patch > Resouce lookup exception message is not available in react UI > - > > Key: RANGER-4090 > URL: https://issues.apache.org/jira/browse/RANGER-4090 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4090.patch, 0002-RANGER-4090.patch > > > Resouce lookup exception message is not available in react UI > Steps to reproduce : > 1. While creating policy enter any resouce name which is not available > Actual : We are not getting any expception message related to these resouce > while resouce lookup > Expected : Like Old ui user should get these expection message for resource > lookup > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4087) Loader is still loading for resource field for policy creation even after Resource lookup API gives 200/204
[ https://issues.apache.org/jira/browse/RANGER-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4087: --- Attachment: 0002-RANGER-4087.patch > Loader is still loading for resource field for policy creation even after > Resource lookup API gives 200/204 > --- > > Key: RANGER-4087 > URL: https://issues.apache.org/jira/browse/RANGER-4087 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4087.patch, 0002-RANGER-4087.patch > > > Loader is still loading for resource field for policy creation even after > Resource lookup API gives 200/204 > Steps to reproduce : > 1. Create a hive Policy > 2. Edit that policy > 3. Go back to ranger home page and again navigate back to policy with edit > option > Actual : Resouce fields are still having loader which seems its still > waiting for resouce even Resource lookup API gives 200/204. > Expected : Loader should not be there after some time -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4073) Groups are not visible in mask and row level policy listing tables.
[ https://issues.apache.org/jira/browse/RANGER-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707166#comment-17707166 ] Dhaval Rajpara commented on RANGER-4073: Committed to the apache [master|https://github.com/apache/ranger/commit/000db1cbeb0f8fed1e02e88edbdc80386023b515] branch. > Groups are not visible in mask and row level policy listing tables. > --- > > Key: RANGER-4073 > URL: https://issues.apache.org/jira/browse/RANGER-4073 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Brijesh Bhalala >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4073.patch > > > 1)Groups are not visible in mask and row level policy listing tables. -- This message was sent by Atlassian Jira (v8.20.10#820010)
