[GitHub] [ranger] icycle77 commented on pull request #71: Resolve ranger-examples-distro module compile error
icycle77 commented on pull request #71: URL: https://github.com/apache/ranger/pull/71#issuecomment-692333429 I wanted to say thanks for putting this out there @PrivateLi , I hit the exact same problem and your patch got me to a successful `mvn package` step. I did see [this note](https://github.com/apache/ranger/blob/master/README.txt#L21-L23) in the readme, looks like they don't take Github PRs yet. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (RANGER-2996) Add search by Roles and Auditor user should be able to see "Roles" tab.
[ https://issues.apache.org/jira/browse/RANGER-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2996: - Attachment: 0001-RANGER-2996.patch > Add search by Roles and Auditor user should be able to see "Roles" tab. > --- > > Key: RANGER-2996 > URL: https://issues.apache.org/jira/browse/RANGER-2996 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2996.patch > > > * Search by Roles Name on > 1) Report page and Policy listing page. > * Auditor user should be able to see Roles tab. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2996) Add search by Roles and Auditor user should be able to see "Roles" tab.
Nitin Galave created RANGER-2996: Summary: Add search by Roles and Auditor user should be able to see "Roles" tab. Key: RANGER-2996 URL: https://issues.apache.org/jira/browse/RANGER-2996 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave * Search by Roles Name on 1) Report page and Policy listing page. * Auditor user should be able to see Roles tab. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2984) “NoSuchMethodErrors” due to multiple versions of com.google.guava:guava:jar
[
https://issues.apache.org/jira/browse/RANGER-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bing-ok updated RANGER-2984:
Description:
h1. Issue description
Hi, there are multiple versions of _*com.google.guava:guava*_ in
_*ranger\unixauthclient*_. As shown in the following dependency tree, according
to Maven's “nearest wins” strategy, only _*com.google.guava:guava:25.1-jre*_
can be loaded, _*com.google.guava:guava:16.0.1*_ will be shadowed.
However, one method defined in shadowed version
_*com.google.guava:guava:16.0.1*_ is referenced by client project
_*org.apache.hadoop:hadoop-auth:3.1.1*_, but missing in the actually loaded
version _*com.google.guava:guava:25.1-jre*_.
For instance, the following missing method(defined in
_*com.google.guava:guava:16.0.1*_) is actually referenced by
_*ranger\unixauthclient*_, which will introduce a runtime error(i.e.,
"NoSuchMethodError") into _*ranger\unixauthclient*_.\
_*Missing method: com.google.common.reflect.TypeToken: java.lang.reflect.Type
access$400(com.google.common.reflect.TypeToken)*_ is invoked by
_*ranger\unixauthclient*_ via the following path:
{noformat}
paths--
ranger\unixauthclient\target\classes
Repositories\org\apache\curator\curator-client\2.12.0\curator-client-2.12.0.jar
Repositories\org\apache\curator\curator-client\2.12.0\curator-client-2.12.0.jar
Repositories\org\apache\curator\curator-client\2.12.0\curator-client-2.12.0.jar
{noformat}
h1. Suggested fixing solutions
1. Upgrade dependency _*org.apache.hadoop:hadoop-auth*_ from _*3.1.1*_ to
*_3.3.0_*. Because the newer version _*org.apache.hadoop:hadoop-auth:3.3.0*_
does not invoke the above missing method, such upgrading can solve the problem.
2. Change dependency _*com.google.guava:guava*_ from _*25.1-jre*_ to
*_24.0-jre_*. Because version *_24.0-jre_* includes the above missing method
and is compatible with other versions of _*com.google.guava:guava*_ .
Please let me know which solution do you prefer? I can submit a PR to fix it.
Thank you very much for your attention.
Best regards,
h1. Dependency tree
{noformat}
[INFO] org.apache.ranger:unixauthclient:jar:3.0.0-SNAPSHOT
[INFO] +- *com.google.guava:guava:jar:25.1-jre:compile*
[INFO] - org.apache.hadoop:hadoop-auth:jar:3.1.1:compile
[INFO] +- org.apache.curator:curator-framework:jar:2.12.0:compile
[INFO] | - org.apache.curator:curator-client:jar:2.12.0:compile
[INFO] | - *(com.google.guava:guava:jar:16.0.1:compile - omitted for conflict
with 25.1-jre)*
[INFO] - (com.google.guava:guava:jar:11.0.2:compile - omitted for conflict with
25.1-jre){noformat}
was:
Hi, there are multiple versions of _*com.google.guava:guava*_ in
_*ranger\unixauthclient*_. As shown in the following dependency tree, according
to Maven's “nearest wins” strategy, only _*com.google.guava:guava:25.1-jre*_
can be loaded, _*com.google.guava:guava:16.0.1*_ will be shadowed.
As _*com.google.guava:guava:16.0.1*_ has not been loaded during the building
process, several methods are missing. However, the missing methods:
1. _*com.google.common.reflect.TypeToken: java.lang.reflect.Type
access$400(com.google.common.reflect.TypeToken)*_
{noformat}
paths--
ranger\unixauthclient\target\classes
Repositories\org\apache\curator\curator-client\2.12.0\curator-client-2.12.0.jar
Repositories\org\apache\curator\curator-client\2.12.0\curator-client-2.12.0.jar
Repositories\org\apache\curator\curator-client\2.12.0\curator-client-2.12.0.jar
{noformat}
The above missing methods are actually referenced by _*ranger\unixauthclient*_,
which will cause “NoSuchMethodErrors” at runtime.
Suggested fixing solutions:
1. Upgrade dependency _*org.apache.hadoop:hadoop-auth*_ from _*3.1.1*_ to
*_3.3.0_*. Because one conflicting library version
_*com.google.guava:guava:16.0.1*_ is transitively introduced by
_*org.apache.hadoop:hadoop-auth:3.3.0*_. Upgrading dependency
_*org.apache.hadoop:hadoop-auth*_ from _*3.1.1*_ to *_3.3.0_* can solve this
dependency conflict.
2. Change dependency _*com.google.guava:guava*_ from _*25.1-jre*_ to
*_24.0-jre_*.
Please let me know which solution do you prefer? I can submit a PR to fix it.
Thank you very much for your attention.
Best regards,
Dependency tree
[INFO] org.apache.ranger:unixauthclient:jar:3.0.0-SNAPSHOT
[INFO] +- *com.google.guava:guava:jar:25.1-jre:compile*
[INFO] - org.apache.hadoop:hadoop-auth:jar:3.1.1:compile
[INFO] +- org.apache.curator:curator-framework:jar:2.12.0:compile
[INFO] | - org.apache.curator:curator-client:jar:2.12.0:compile
[INFO] | - *(com.google.guava:guava:jar:16.0.1:compile - omitted for conflict
with 25.1-jre)*
[INFO] - (com.google.guava:guava:jar:11.0.2:compile - omitted for conflict
with 25.1-jre)
> “NoSuchMethodErrors” due to multiple versions of com.google.guava:guava:jar
> ---
>
> Key: RANGER-2984
>
[jira] [Updated] (RANGER-2995) Add 'exclude service users' option in URL param
[ https://issues.apache.org/jira/browse/RANGER-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2995: - Attachment: 0001-RANGER-2995.patch > Add 'exclude service users' option in URL param > --- > > Key: RANGER-2995 > URL: https://issues.apache.org/jira/browse/RANGER-2995 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2995.patch > > > Add ‘Exclude Service Users’ option in url-param. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2995) Add 'exclude service users' option in URL param
Nitin Galave created RANGER-2995: Summary: Add 'exclude service users' option in URL param Key: RANGER-2995 URL: https://issues.apache.org/jira/browse/RANGER-2995 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave Add ‘Exclude Service Users’ option in url-param. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 72867: RANGER-2988 : Role Name Search filter is not available on policy listing page.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72867/ --- Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Gautam Borad, Jayendra Parab, Kishor Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mahesh Bandal, Mehul Parikh, Pradeep Agrawal, and Velmurugan Periasamy. Bugs: RANGER-2988 https://issues.apache.org/jira/browse/RANGER-2988 Repository: ranger Description --- Actual Result: Role Name Search filter is not available on policy listing page Expected Result: Role Name Search filter should be available on policy listing page Diffs - agents-common/src/main/java/org/apache/ranger/plugin/store/AbstractPredicateUtil.java 85fa213 security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 98a8596 security-admin/src/main/webapp/scripts/modules/globalize/message/en.js f92e985 security-admin/src/main/webapp/scripts/views/policies/NRangerPolicyTableLayout.js 79632cf security-admin/src/main/webapp/scripts/views/policies/RangerPolicyTableLayout.js 9656fb5 Diff: https://reviews.apache.org/r/72867/diff/1/ Testing --- Tested that Role Name Search filter rendered on policy listing page properly. Thanks, Nitin Galave
[jira] [Updated] (RANGER-2767) Ranger showing only 100 services in ranger admin ui
[ https://issues.apache.org/jira/browse/RANGER-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2767: - Attachment: (was: 0002-RANGER-2767.patch) > Ranger showing only 100 services in ranger admin ui > --- > > Key: RANGER-2767 > URL: https://issues.apache.org/jira/browse/RANGER-2767 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2767.patch, 0002-RANGER-2767.patch > > > Ranger only shows 100 services, As in the future, it's expected to have more > service, it may be recommended to increase the limit to 200. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2767) Ranger showing only 100 services in ranger admin ui
[ https://issues.apache.org/jira/browse/RANGER-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2767: - Attachment: 0002-RANGER-2767.patch > Ranger showing only 100 services in ranger admin ui > --- > > Key: RANGER-2767 > URL: https://issues.apache.org/jira/browse/RANGER-2767 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2767.patch, 0002-RANGER-2767.patch > > > Ranger only shows 100 services, As in the future, it's expected to have more > service, it may be recommended to increase the limit to 200. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2993) Syncing AD/LDAP groups with special characters causing Usersync to get stuck
[
https://issues.apache.org/jira/browse/RANGER-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195355#comment-17195355
]
Georgi Ivanov commented on RANGER-2993:
---
Hi, I was able to bypass the special characters by crafting an LDAP filter that
excludes the group in question. The error was not returned by UserSync, however
the overall behaviour was kept, i.e. usersync finished successfully the initial
run, but did not did a delta run, i.e. it "got stuck" in the sleep and never
recovered.
> Syncing AD/LDAP groups with special characters causing Usersync to get stuck
>
>
> Key: RANGER-2993
> URL: https://issues.apache.org/jira/browse/RANGER-2993
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 2.0.0
>Reporter: Georgi Ivanov
>Priority: Major
>
> We are running Ranger on kubernetes. The usersync component runs in a
> separate pod as a standalone component. During the initial sync, it throws an
> error about a AD/LDAP group that contains a special character.
>
> {code:java}
> 10 Sep 2020 03:24:01 ERROR LdapDeltaUserGroupBuilder [UnixUserSyncThread] -
> sink.addOrUpdateGroup failed with exception: Failed to add addorUpdate group
> user info, for group: s-TFxLabRun%, users: [...]
> 10 Sep 2020 03:24:01 ERROR LdapPolicyMgrUserGroupBuilder [UnixUserSyncThread]
> - Failed to add addorUpdate group user info{code}
> And after that the sync does not continue to the next cycle.
> After 3-4 hours after this error (no logs from the LdapDeltaUserGroupBuilder
> or LdapPolicyMgrUserGroupBuilder during that time) we see this log entry
> {code:java}
> 10 Sep 2020 06:38:27 INFO UserGroupSync [UnixUserSyncThread] - End: initial
> load of user/group from source==>sink
> 10 Sep 2020 06:38:27 INFO UserGroupSync [UnixUserSyncThread] - Done
> initializing user/group source and sink{code}
>
> And no more logs after that
> A strace on the process shows it's stuck in a sleep
> {code:java}
> # jps
> 226 UnixAuthenticationService
> 2242 Jps
> # strace -p 226
> strace: Process 226 attached
> futex(0x7f637e9149d0, FUTEX_WAIT, 227, NULL {code}
>
> Jstack also shows the what the UnixUserSyncThread is in waiting state
> (sleeping). There are some locked threads but I don't think they are related
> to the bug.
>
> {noformat}
> # jstack 226
> 2020-09-11 11:22:37
> Full thread dump OpenJDK 64-Bit Server VM (25.232-b09 mixed mode):"Attach
> Listener" #1657 daemon prio=9 os_prio=0 tid=0x7f6350001000 nid=0x798
> waiting on condition [0x]
>java.lang.Thread.State:
> RUNNABLE"org.apache.hadoop.fs.FileSystem$Statistics$StatisticsDataReferenceCleaner"
> #12 daemon prio=5 os_prio=0 tid=0x7f633c2ac800 nid=0xf0 in Object.wait()
> [0x7f636626a000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0xd56d46e0> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
> - locked <0xd56d46e0> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
> at
> org.apache.hadoop.fs.FileSystem$Statistics$StatisticsDataReferenceCleaner.run(FileSystem.java:3806)
> at java.lang.Thread.run(Thread.java:748)"UnixUserSyncThread" #8 prio=5
> os_prio=0 tid=0x7f6378321800 nid=0xec waiting on condition
> [0x7f63663a4000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:79)
> at java.lang.Thread.run(Thread.java:748)"Service Thread" #7 daemon
> prio=9 os_prio=0 tid=0x7f63780b4800 nid=0xea runnable [0x]
>java.lang.Thread.State: RUNNABLE"C1 CompilerThread1" #6 daemon prio=9
> os_prio=0 tid=0x7f63780b1000 nid=0xe9 waiting on condition
> [0x]
>java.lang.Thread.State: RUNNABLE"C2 CompilerThread0" #5 daemon prio=9
> os_prio=0 tid=0x7f63780af000 nid=0xe8 waiting on condition
> [0x]
>java.lang.Thread.State: RUNNABLE"Signal Dispatcher" #4 daemon prio=9
> os_prio=0 tid=0x7f63780ad800 nid=0xe7 runnable [0x]
>java.lang.Thread.State: RUNNABLE"Finalizer" #3 daemon prio=8 os_prio=0
> tid=0x7f637807c000 nid=0xe6 in Object.wait() [0x7f6366e9]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
> - locked <0xd5588a40> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
> at
>
[jira] [Created] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency
Georgi Ivanov created RANGER-2994: - Summary: ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency Key: RANGER-2994 URL: https://issues.apache.org/jira/browse/RANGER-2994 Project: Ranger Issue Type: Bug Components: plugins Reporter: Georgi Ivanov Ranger 2.1.0 release cannot compile due to broken kylin maven dependency. the kylin version is set to 2.6.4 in the main project pom.xml 2.6.4 plugin-kylin/pom.xml ranger-kylin-plugin-shim/pom.xml both reference kylin-server-base which has dependency on kylin-datasource-sdk which in turn has dependency on calcite-linq4j-1.16.0-kylin-r2.jar which is not available. mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy -Dartifact=org.apache.calcite:calcite-linq4j:jar:1.16.0-kylin-r2 -DoutputDirectory=./ fails and [https://mvnrepository.com/artifact/org.apache.kylin/kylin-datasource-sdk/2.6.4] shows the broken dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2767) Ranger showing only 100 services in ranger admin ui
[ https://issues.apache.org/jira/browse/RANGER-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2767: - Attachment: 0002-RANGER-2767.patch > Ranger showing only 100 services in ranger admin ui > --- > > Key: RANGER-2767 > URL: https://issues.apache.org/jira/browse/RANGER-2767 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2767.patch, 0002-RANGER-2767.patch > > > Ranger only shows 100 services, As in the future, it's expected to have more > service, it may be recommended to increase the limit to 200. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2988) Role Name Search filter is not available on policy listing page
[ https://issues.apache.org/jira/browse/RANGER-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2988: - Attachment: 0002-RANGER-2988.patch > Role Name Search filter is not available on policy listing page > --- > > Key: RANGER-2988 > URL: https://issues.apache.org/jira/browse/RANGER-2988 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2988.patch, 0002-RANGER-2988.patch > > > Actual Result: Role Name Search filter is not available on policy listing page > Expected Result: Role Name Search filter should be available on policy > listing page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2988) Role Name Search filter is not available on policy listing page
[ https://issues.apache.org/jira/browse/RANGER-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-2988: - Attachment: (was: 0002-RANGER-2988.patch) > Role Name Search filter is not available on policy listing page > --- > > Key: RANGER-2988 > URL: https://issues.apache.org/jira/browse/RANGER-2988 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: 0001-RANGER-2988.patch > > > Actual Result: Role Name Search filter is not available on policy listing page > Expected Result: Role Name Search filter should be available on policy > listing page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2981) Unwanted popup display on Security Zone Tab.
[
https://issues.apache.org/jira/browse/RANGER-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave resolved RANGER-2981.
--
Resolution: Fixed
> Unwanted popup display on Security Zone Tab.
>
>
> Key: RANGER-2981
> URL: https://issues.apache.org/jira/browse/RANGER-2981
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: 0001-RANGER-2981.patch, ZoneCreateEditPage.png,
> ZoneListingpage.png
>
>
> Step :
> 1) Login to Ranger UI.
> 2) Go to Audit ==> Access tab.
> 3) Click on table row, Policy detail popup appear.
> 4) Then Go to security zone tab.
> 5) Click on table Row in Zone Listing page and Zone create/edit page.
> 6) {color:#ff}Unwanted Policy detail popup appear{color}.
> 7) Please Refer screenshot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-2981) Unwanted popup display on Security Zone Tab.
[
https://issues.apache.org/jira/browse/RANGER-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195316#comment-17195316
]
Nitin Galave commented on RANGER-2981:
--
Committed to
[ranger-2.2|https://github.com/apache/ranger/commit/05a6974bf5be84cb5338e97769d0756a08ee1090]
branch.
> Unwanted popup display on Security Zone Tab.
>
>
> Key: RANGER-2981
> URL: https://issues.apache.org/jira/browse/RANGER-2981
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: 0001-RANGER-2981.patch, ZoneCreateEditPage.png,
> ZoneListingpage.png
>
>
> Step :
> 1) Login to Ranger UI.
> 2) Go to Audit ==> Access tab.
> 3) Click on table row, Policy detail popup appear.
> 4) Then Go to security zone tab.
> 5) Click on table Row in Zone Listing page and Zone create/edit page.
> 6) {color:#ff}Unwanted Policy detail popup appear{color}.
> 7) Please Refer screenshot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-2981) Unwanted popup display on Security Zone Tab.
[
https://issues.apache.org/jira/browse/RANGER-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195313#comment-17195313
]
Nitin Galave commented on RANGER-2981:
--
Committed to [apache
master|https://github.com/apache/ranger/commit/a048d5db4b5171544371b80263a75fefc4e5b20f]
branch.
> Unwanted popup display on Security Zone Tab.
>
>
> Key: RANGER-2981
> URL: https://issues.apache.org/jira/browse/RANGER-2981
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: 0001-RANGER-2981.patch, ZoneCreateEditPage.png,
> ZoneListingpage.png
>
>
> Step :
> 1) Login to Ranger UI.
> 2) Go to Audit ==> Access tab.
> 3) Click on table row, Policy detail popup appear.
> 4) Then Go to security zone tab.
> 5) Click on table Row in Zone Listing page and Zone create/edit page.
> 6) {color:#ff}Unwanted Policy detail popup appear{color}.
> 7) Please Refer screenshot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
