[jira] [Commented] (RANGER-4791) Fixing build issue for Phantomjs Auto configuration failed due to OPEN_SSL
[
https://issues.apache.org/jira/browse/RANGER-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846186#comment-17846186
]
Mugdha Varadkar commented on RANGER-4791:
-
[~pushkargogte], Please help in verifying the attached patch on Docker build.
Thanks
> Fixing build issue for Phantomjs Auto configuration failed due to OPEN_SSL
> --
>
> Key: RANGER-4791
> URL: https://issues.apache.org/jira/browse/RANGER-4791
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Attachments: 0001-RANGER-4791.patch
>
>
> Ranger build for redhat9 is failing for security-admin module for phantomjs
> auto configuration failed.
> Below is the log trace,
> {code}
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.533:INFO
> [launcher]: Starting browser PhantomJS
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.565:ERROR
> [phantomjs.launcher]: Auto configuration failed
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25066067:DSO support routines:DLFCN_LOAD:could not load
> the shared library:dso_dlfcn.c:185:filename(libproviders.so):
> libproviders.so: cannot open shared object file: No such file or directory
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25070067:DSO support routines:DSO_load:could not load
> the shared library:dso_lib.c:244:
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E07506E:configuration file
> routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
> path=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E076071:configuration file routines:MODULE_RUN:unknown
> module name:conf_mod.c:222:module=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
> [launcher]: Cannot start PhantomJS
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] Auto configuration
> failed
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25066067:DSO support routines:DLFCN_LOAD:could not load
> the shared library:dso_dlfcn.c:185:filename(libproviders.so):
> libproviders.so: cannot open shared object file: No such file or directory
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25070067:DSO support routines:DSO_load:could not load
> the shared library:dso_lib.c:244:
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E07506E:configuration file
> routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
> path=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E076071:configuration file routines:MODULE_RUN:unknown
> module name:conf_mod.c:222:module=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
> [launcher]: PhantomJS stdout:
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
> [launcher]: PhantomJS stderr: Auto configuration failed
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4791) Fixing build issue for Phantomjs Auto configuration failed due to OPEN_SSL
[
https://issues.apache.org/jira/browse/RANGER-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated RANGER-4791:
Attachment: 0001-RANGER-4791.patch
> Fixing build issue for Phantomjs Auto configuration failed due to OPEN_SSL
> --
>
> Key: RANGER-4791
> URL: https://issues.apache.org/jira/browse/RANGER-4791
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Attachments: 0001-RANGER-4791.patch
>
>
> Ranger build for redhat9 is failing for security-admin module for phantomjs
> auto configuration failed.
> Below is the log trace,
> {code}
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.533:INFO
> [launcher]: Starting browser PhantomJS
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.565:ERROR
> [phantomjs.launcher]: Auto configuration failed
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25066067:DSO support routines:DLFCN_LOAD:could not load
> the shared library:dso_dlfcn.c:185:filename(libproviders.so):
> libproviders.so: cannot open shared object file: No such file or directory
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25070067:DSO support routines:DSO_load:could not load
> the shared library:dso_lib.c:244:
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E07506E:configuration file
> routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
> path=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E076071:configuration file routines:MODULE_RUN:unknown
> module name:conf_mod.c:222:module=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
> [launcher]: Cannot start PhantomJS
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] Auto configuration
> failed
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25066067:DSO support routines:DLFCN_LOAD:could not load
> the shared library:dso_dlfcn.c:185:filename(libproviders.so):
> libproviders.so: cannot open shared object file: No such file or directory
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:25070067:DSO support routines:DSO_load:could not load
> the shared library:dso_lib.c:244:
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E07506E:configuration file
> routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
> path=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 139820265396032:error:0E076071:configuration file routines:MODULE_RUN:unknown
> module name:conf_mod.c:222:module=providers
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO]
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
> [launcher]: PhantomJS stdout:
> 10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
> [launcher]: PhantomJS stderr: Auto configuration failed
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4791) Fixing build issue for Phantomjs Auto configuration failed due to OPEN_SSL
Mugdha Varadkar created RANGER-4791:
---
Summary: Fixing build issue for Phantomjs Auto configuration
failed due to OPEN_SSL
Key: RANGER-4791
URL: https://issues.apache.org/jira/browse/RANGER-4791
Project: Ranger
Issue Type: Bug
Components: admin
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Ranger build for redhat9 is failing for security-admin module for phantomjs
auto configuration failed.
Below is the log trace,
{code}
10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.533:INFO
[launcher]: Starting browser PhantomJS
10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.565:ERROR
[phantomjs.launcher]: Auto configuration failed
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:25066067:DSO support routines:DLFCN_LOAD:could not load
the shared library:dso_dlfcn.c:185:filename(libproviders.so): libproviders.so:
cannot open shared object file: No such file or directory
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:25070067:DSO support routines:DSO_load:could not load the
shared library:dso_lib.c:244:
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:0E076071:configuration file routines:MODULE_RUN:unknown
module name:conf_mod.c:222:module=providers
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
[launcher]: Cannot start PhantomJS
10:53:58 2024/05/08 05:23:58 INFO: [INFO] Auto configuration failed
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:25066067:DSO support routines:DLFCN_LOAD:could not load
the shared library:dso_dlfcn.c:185:filename(libproviders.so): libproviders.so:
cannot open shared object file: No such file or directory
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:25070067:DSO support routines:DSO_load:could not load the
shared library:dso_lib.c:244:
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
139820265396032:error:0E076071:configuration file routines:MODULE_RUN:unknown
module name:conf_mod.c:222:module=providers
10:53:58 2024/05/08 05:23:58 INFO: [INFO]
10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
[launcher]: PhantomJS stdout:
10:53:58 2024/05/08 05:23:58 INFO: [INFO] 08 05 2024 05:23:58.571:ERROR
[launcher]: PhantomJS stderr: Auto configuration failed
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] RANGER-XXXX: Fix problem with ElasticSearch as Audit database [ranger]
FerArribas14 commented on PR #314: URL: https://github.com/apache/ranger/pull/314#issuecomment-2109057763 Hi, what version of elasticsearch are you testing on localhost:9200? I can't get it to write audit events to elasticsearch. There are no errors in the ranger admin logs and the index has been created correctly. I have everything deployed in docker. I have created an elasticsearch service in docker compose. Thanks, -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] RANGER-XXXX: Fix problem with ElasticSearch as Audit database [ranger]
ognjen-it opened a new pull request, #314:
URL: https://github.com/apache/ranger/pull/314
## What changes were proposed in this pull request?
I tried to create a user on Apache Jira but I've not received confirmation
yet. Until that, I'm opening this pull request for all whos seeing problems
with audit. I'm not sure if I need to do the same on the master branch?
1. Lucene version - fixed problem with writing data to ElasticSearch
**Error**: java.lang.NoSuchFieldError: LUCENE_8_5_1
I tried to change minor version one by one, but only latest version fit for
me.
Changes:
- agents-audit/pom.xml: 311
- pom.xml: 241
2. Elastic search protocol - fixed problem with changing protocol
Even though I changed ranger.audit.elasticsearch.protocol from http to
https, audit plugin still using http protocol.
Changes:
- security-admin/scripts/ranger-admin-site-template.xml: 167-170
- security-admin/scripts/setup.sh: 79, 794-797
- security-admin/scripts/upgrade_admin.py: 116
- security-admin/src/main/resources/conf.dist/ranger-admin-site.xml: 53-57
-
security-admin/src/test/java/org/apache/ranger/elasticsearch/ElasticSearchAccessAuditsServiceTest.java:
56
3. Audit plugin - cannot write audit to ES
**Error**: bootstrap method initialization exception
After changing the version of httpcomponents I started seeing audit
Changes:
- pom.xml: 137, 138, 140
4. Ranger admin console - Audit show 1-1-1970
**Erro**: Error converting value to date. Value = 2024-05-13T13:08:47.905Z
Even though evtTime was ok in ElasticSearch, ranger couldn't show it on GUI.
Changes:
-
security-admin/src/main/java/org/apache/ranger/elasticsearch/ElasticSearchAccessAuditsService.java:
260
-
security-admin/src/main/java/org/apache/ranger/solr/SolrAccessAuditsService.java:
239
## How was this patch tested?
I tested it manually.
ElasticSearch:
https://github.com/apache/ranger/assets/44586606/0ca72983-4cea-4484-9cf4-845ee5bd0a91";>
Ranger:
https://github.com/apache/ranger/assets/44586606/d52071d7-fe04-4199-a45b-3f7d1ec55974";>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[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&focusedCommentId=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)
Re: Review Request 74982: RANGER-4681: Audit logs for Mask & Row policy does not show policy condition under policy item
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74982/#review226431 --- Ship it! Ship It! - Mugdha Varadkar On May 13, 2024, 9:48 a.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74982/ > --- > > (Updated May 13, 2024, 9:48 a.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4681 > https://issues.apache.org/jira/browse/RANGER-4681 > > > Repository: ranger > > > Description > --- > > Audit logs for Mask & Row policy does not show policy condition under policy > item. > > > > Steps to repro: > > 1) Inside Hive service, navigate hive masking policy listing page. > > 2) Click on "Add New Policy", add all the details. Under policy item section > add policy condition. Now save the policy > > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > One modal would be opened which show all the details for the policy > > 4) Under "Row Level Filter Policy Items" section we would not see policy > condition details. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/styles/style.css e6b767f5e > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyLogs.jsx > acd4f5825 > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx > 7dd2de84f > > > Diff: https://reviews.apache.org/r/74982/diff/2/ > > > Testing > --- > > Applied the patch on a cluster and tested the following UI scenarios :- > 1)Policy CRUD operations. > 2)Resource based & tag based policy modules. > 3)Audit admin table. > > > Thanks, > > Brijesh Bhalala > >
Re: Review Request 74982: RANGER-4681: Audit logs for Mask & Row policy does not show policy condition under policy item
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74982/#review226430 --- Ship it! Ship It! - Dhaval Rajpara On May 13, 2024, 9:48 a.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74982/ > --- > > (Updated May 13, 2024, 9:48 a.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4681 > https://issues.apache.org/jira/browse/RANGER-4681 > > > Repository: ranger > > > Description > --- > > Audit logs for Mask & Row policy does not show policy condition under policy > item. > > > > Steps to repro: > > 1) Inside Hive service, navigate hive masking policy listing page. > > 2) Click on "Add New Policy", add all the details. Under policy item section > add policy condition. Now save the policy > > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > One modal would be opened which show all the details for the policy > > 4) Under "Row Level Filter Policy Items" section we would not see policy > condition details. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/styles/style.css e6b767f5e > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyLogs.jsx > acd4f5825 > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx > 7dd2de84f > > > Diff: https://reviews.apache.org/r/74982/diff/2/ > > > Testing > --- > > Applied the patch on a cluster and tested the following UI scenarios :- > 1)Policy CRUD operations. > 2)Resource based & tag based policy modules. > 3)Audit admin table. > > > Thanks, > > Brijesh Bhalala > >
[jira] [Updated] (RANGER-4681) Audit logs for Mask & Row policy does not show policy condition under policy item
[ https://issues.apache.org/jira/browse/RANGER-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4681: Attachment: 0004-RANGER-4681.patch > Audit logs for Mask & Row policy does not show policy condition under policy > item > - > > Key: RANGER-4681 > URL: https://issues.apache.org/jira/browse/RANGER-4681 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4681.patch, 0002-RANGER-4681.patch, > 0003-RANGER-4681.patch, 0004-RANGER-4681.patch > > > Audit logs for Mask & Row policy does not show policy condition under policy > item. > > Steps to repro: > 1) Inside Hive service, navigate hive masking policy listing page. > 2) Click on "Add New Policy", add all the details. Under policy item section > add policy condition. Now save the policy > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > One modal would be opened which show all the details for the policy > 4) Under "Row Level Filter Policy Items" section we would not see policy > condition details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74982: RANGER-4681: Audit logs for Mask & Row policy does not show policy condition under policy item
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74982/ --- (Updated May 13, 2024, 9:48 a.m.) Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4681 https://issues.apache.org/jira/browse/RANGER-4681 Repository: ranger Description --- Audit logs for Mask & Row policy does not show policy condition under policy item. Steps to repro: 1) Inside Hive service, navigate hive masking policy listing page. 2) Click on "Add New Policy", add all the details. Under policy item section add policy condition. Now save the policy 3) Go to Audits, Admin page, click on the audit record of above newly policy. One modal would be opened which show all the details for the policy 4) Under "Row Level Filter Policy Items" section we would not see policy condition details. Diffs (updated) - security-admin/src/main/webapp/react-webapp/src/styles/style.css e6b767f5e security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyLogs.jsx acd4f5825 security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx 7dd2de84f Diff: https://reviews.apache.org/r/74982/diff/2/ Changes: https://reviews.apache.org/r/74982/diff/1-2/ Testing --- Applied the patch on a cluster and tested the following UI scenarios :- 1)Policy CRUD operations. 2)Resource based & tag based policy modules. 3)Audit admin table. Thanks, Brijesh Bhalala
[jira] [Updated] (RANGER-4681) Audit logs for Mask & Row policy does not show policy condition under policy item
[ https://issues.apache.org/jira/browse/RANGER-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4681: Attachment: (was: 0004-RANGER_4681.patch) > Audit logs for Mask & Row policy does not show policy condition under policy > item > - > > Key: RANGER-4681 > URL: https://issues.apache.org/jira/browse/RANGER-4681 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4681.patch, 0002-RANGER-4681.patch, > 0003-RANGER-4681.patch > > > Audit logs for Mask & Row policy does not show policy condition under policy > item. > > Steps to repro: > 1) Inside Hive service, navigate hive masking policy listing page. > 2) Click on "Add New Policy", add all the details. Under policy item section > add policy condition. Now save the policy > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > One modal would be opened which show all the details for the policy > 4) Under "Row Level Filter Policy Items" section we would not see policy > condition details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4681) Audit logs for Mask & Row policy does not show policy condition under policy item
[ https://issues.apache.org/jira/browse/RANGER-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4681: Attachment: 0004-RANGER_4681.patch > Audit logs for Mask & Row policy does not show policy condition under policy > item > - > > Key: RANGER-4681 > URL: https://issues.apache.org/jira/browse/RANGER-4681 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4681.patch, 0002-RANGER-4681.patch, > 0003-RANGER-4681.patch > > > Audit logs for Mask & Row policy does not show policy condition under policy > item. > > Steps to repro: > 1) Inside Hive service, navigate hive masking policy listing page. > 2) Click on "Add New Policy", add all the details. Under policy item section > add policy condition. Now save the policy > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > One modal would be opened which show all the details for the policy > 4) Under "Row Level Filter Policy Items" section we would not see policy > condition details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74982: RANGER-4681: Audit logs for Mask & Row policy does not show policy condition under policy item
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74982/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4681 https://issues.apache.org/jira/browse/RANGER-4681 Repository: ranger Description --- Audit logs for Mask & Row policy does not show policy condition under policy item. Steps to repro: 1) Inside Hive service, navigate hive masking policy listing page. 2) Click on "Add New Policy", add all the details. Under policy item section add policy condition. Now save the policy 3) Go to Audits, Admin page, click on the audit record of above newly policy. One modal would be opened which show all the details for the policy 4) Under "Row Level Filter Policy Items" section we would not see policy condition details. Diffs - security-admin/src/main/webapp/react-webapp/src/styles/style.css f47d8518e security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyLogs.jsx acd4f5825 security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx 7dd2de84f Diff: https://reviews.apache.org/r/74982/diff/1/ Testing --- Applied the patch on a cluster and tested the following UI scenarios :- 1)Policy CRUD operations. 2)Resource based & tag based policy modules. 3)Audit admin table. Thanks, Brijesh Bhalala
