[jira] [Commented] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server

[kirby zhou (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689578#comment-17689578
 ] 

kirby zhou commented on RANGER-3756:


I had encounter this bug with the cloud service of mysql provided by Tencent 
Cloud. 

[http://cloud.tencent.com|http://cloud.tencent.com/] 【China】or  
[https://www.tencentcloud.com/]  【international】

It happens at the ranger-2.3 branch.

> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
>  Issue Type: Bug
>  Components: admin
>Reporter: kirby zhou
>Priority: Critical
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO  
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY 
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL, 
> change_timestamp 
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id)) 
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR 
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1. 
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS 
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp 
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id)) 
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY 
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional 
> context.  These statements are also not allowed in a function or trigger 
> because functions and triggers are also considered to be multi-statement 
> transactions.
>         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
>         at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
>         at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
>         at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
>         at 
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
>         at 
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.5.2.v20140319-9ad6abd): 
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception: 
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call: 
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM 
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM 
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN 
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind 
> => [2 parameters bound] Query: 
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId" 
> referenceClass=XXRMSResourceMapping sql="DELETE FROM 
> TL_x_rms_resource_mapping")
> {code}
>  
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed 
> outside transactional context.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [ranger] xyueji closed pull request #165: fix deltaSyncUserTimeStamp and deltaSyncGroupTimeStamp of the ugsync

[via GitHub]

xyueji closed pull request #165: fix deltaSyncUserTimeStamp and 
deltaSyncGroupTimeStamp of the ugsync
URL: https://github.com/apache/ranger/pull/165


-- 
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] [Assigned] (RANGER-4091) Policy condition & Permission window should close by any click events

[Brijesh Bhalala (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brijesh Bhalala reassigned RANGER-4091:
---

Assignee: Brijesh Bhalala

> Policy condition  & Permission window should close by any click events
> --
>
> Key: RANGER-4091
> URL: https://issues.apache.org/jira/browse/RANGER-4091
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Brijesh Bhalala
>Priority: Critical
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 9.14.47 PM.png
>
>
> Policy condition window Overlaps with Policy permisions window as Policy 
> condition  & Permission window is not closing by any click events
> Steps to reproduce :
> 1. Try to create any tag based policy 
> 2. Click on Policy condition + icon
> 3. Click on permission + icon
> Actual :  Policy condition  & Permission window is not closing by any click 
> events
> Expected :   Policy condition  & Permission window should close by any click 
> events



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74112: RANGER-3903:Improvement in RangerPolicyDeltaUtil--> applyDeltas method

[Ramachandran Krishnan]

> On Jan. 29, 2023, 11:16 a.m., Kirby Zhou wrote:
> > agents-common/src/main/java/org/apache/ranger/plugin/util/RangerPolicyDeltaUtil.java
> > Lines 121 (patched)
> > 
> >
> > just call ret.addAll(policesIdMap.values()) ?
> 
> Ramachandran Krishnan wrote:
> Done

Madhan,
I feel we can consider this fix which will reduce the time complexity from O(N 
* M) to O(N + M) and simplify the code .


- Ramachandran


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74112/#review225137
---


On Jan. 29, 2023, 1:01 p.m., Ramachandran Krishnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74112/
> ---
> 
> (Updated Jan. 29, 2023, 1:01 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Kirby Zhou, Abhay Kulkarni, 
> Madhan Neethiraj, Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, 
> Selvamohan Neethiraj, Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-3903
> https://issues.apache.org/jira/browse/RANGER-3903
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> After going through the below code snippets in the master branch 
> 
> while (iter.hasNext()) {
> RangerPolicy policy = iter.next();
> if (policyId.equals(policy.getId()) && (changeType == 
> RangerPolicyDelta.CHANGE_TYPE_POLICY_DELETE || changeType == 
> RangerPolicyDelta.CHANGE_TYPE_POLICY_UPDATE)) {
> deletedPolicies.add(policy);
> iter.remove();
> }
> }
> switch (changeType) {
> case RangerPolicyDelta.CHANGE_TYPE_POLICY_CREATE:
> {
> if (CollectionUtils.isNotEmpty(deletedPolicies)) {
> LOG.warn("Unexpected: found existing policy for 
> CHANGE_TYPE_POLICY_CREATE: " + Arrays.toString(deletedPolicies.toArray()));
> }
> break;
> }
> case RangerPolicyDelta.CHANGE_TYPE_POLICY_UPDATE:
> {
> if (CollectionUtils.isEmpty(deletedPolicies) || 
> deletedPolicies.size() > 1) {
> LOG.warn("Unexpected: found no policy or multiple policies 
> for CHANGE_TYPE_POLICY_UPDATE: " + 
> Arrays.toString(deletedPolicies.toArray()));
> }
> break;
> }
> case RangerPolicyDelta.CHANGE_TYPE_POLICY_DELETE:
> {
> if (CollectionUtils.isEmpty(deletedPolicies) || 
> deletedPolicies.size() > 1) {
> LOG.warn("Unexpected: found no policy or multiple policies 
> for CHANGE_TYPE_POLICY_DELETE: " + 
> Arrays.toString(deletedPolicies.toArray()));
> }
> break;
> }
> default:
> break;
> }
> 
> 1st#improvement:
> 
> From the above code, we iterate delta policies and check if this policy 
> exists in the existing policy, we add that to deletePolicies list.
> 
> The delta change type condition for created/updated/deleted is added on top 
> of the if the condition so adding the condition again is not necessary 
> 
> 2nd#improvement:
> From the above code, we see for each element in the deltas,we iterate 
> policies and check if this delta policy exists in the existing policy, we add 
> that to deletePolicies list.
> 
> Solution:
> We need to use Map instead of iterating policies for every element of deltas 
> --> Map policiesIdMap
> Building index map key will be policyId and value will be policy associated 
> with the same policyId
> For  each policy in the deltas ,we check on the policiesIdMap whether the 
> same policyId is present or not ?.
> if yes, we will add all the associated policy  into deletedPolicy variable 
> and remove the policyId from policiesIdMap
> After an end of the iteration,we will iterate the policiesIdMap and get all 
> the policy associated with policyId and add into result set
> 
> This will give better performance when the policies list is huge.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerPolicyDeltaUtil.java
>  e9223fe69 
> 
> 
> Diff: https://reviews.apache.org/r/74112/diff/9/
> 
> 
> Testing
> ---
> 
> Tested the below Rest API's to make sure everything works fine
> 
> 1.  ServiceREST Rest API :GET /plugins/policies/download/{serviceName}
> 
> 2.  ServiceREST Rest API :GET /plugins/secure/policies/download/{serviceName}
> 
> 
> Thanks,
> 
> Ramachandran Krishnan
> 
>

[jira] [Commented] (RANGER-3998) Support Ranger KMS integration with AWS KMS

[kirby zhou (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689467#comment-17689467
 ] 

kirby zhou commented on RANGER-3998:


Anybody have more ideas ? Can help to commit this?

> Support Ranger KMS integration with AWS KMS
> ---
>
> Key: RANGER-3998
> URL: https://issues.apache.org/jira/browse/RANGER-3998
> Project: Ranger
>  Issue Type: Improvement
>  Components: kms
>Affects Versions: 3.0.0, 2.4.0
>Reporter: kirby zhou
>Assignee: kirby zhou
>Priority: Major
>
> AWS KMS is widely used by many customers.
> Therefore, RangerKMS should support hosting MasterKey to AWS KMS.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74308: RANGER-3999: Implement more efficient way to handle _any access authorization - Part 3

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74308/#review225188
---


Ship it!




Ship It!

- Madhan Neethiraj


On Feb. 16, 2023, 1:31 a.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74308/
> ---
> 
> (Updated Feb. 16, 2023, 1:31 a.m.)
> 
> 
> Review request for ranger, madhan and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-3999
> https://issues.apache.org/jira/browse/RANGER-3999
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When ANY_ACCESS is requested, the policy matching algorithm returns match if 
> match-type is not NONE. However, the current check for ANY_ACCESS checks not 
> only the request's access-type but also the value in the request's context. 
> As the request's context's attribute ISANYACCESS may be set up for processing 
> any of the multiple accesses specified in the context's ACCESSTYPES 
> attribute, only request's access-type needs to be checked to determine if the 
> policy matches.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
>  9a0df550c 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerAccessRequestUtil.java
>  a51f2322a 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/policyengine/TestPolicyEngine.java
>  eb3d0ff46 
>   agents-common/src/test/resources/policyengine/test_policyengine_hive.json 
> 0544feb14 
> 
> 
> Diff: https://reviews.apache.org/r/74308/diff/2/
> 
> 
> Testing
> ---
> 
> Compiles clean and passes all unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 74308: RANGER-3999: Implement more efficient way to handle _any access authorization - Part 3

[Abhay Kulkarni]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74308/
---

(Updated Feb. 16, 2023, 1:31 a.m.)


Review request for ranger, madhan and Madhan Neethiraj.


Changes
---

Added unit tests


Bugs: RANGER-3999
https://issues.apache.org/jira/browse/RANGER-3999


Repository: ranger


Description
---

When ANY_ACCESS is requested, the policy matching algorithm returns match if 
match-type is not NONE. However, the current check for ANY_ACCESS checks not 
only the request's access-type but also the value in the request's context. As 
the request's context's attribute ISANYACCESS may be set up for processing any 
of the multiple accesses specified in the context's ACCESSTYPES attribute, only 
request's access-type needs to be checked to determine if the policy matches.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
 9a0df550c 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerAccessRequestUtil.java
 a51f2322a 
  
agents-common/src/test/java/org/apache/ranger/plugin/policyengine/TestPolicyEngine.java
 eb3d0ff46 
  agents-common/src/test/resources/policyengine/test_policyengine_hive.json 
0544feb14 


Diff: https://reviews.apache.org/r/74308/diff/2/

Changes: https://reviews.apache.org/r/74308/diff/1-2/


Testing
---

Compiles clean and passes all unit tests.


Thanks,

Abhay Kulkarni

[jira] [Commented] (RANGER-4072) setup CI using Github action

[Abhishek Kumar (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689371#comment-17689371
 ] 

Abhishek Kumar commented on RANGER-4072:


Merged to master: 
[https://github.com/apache/ranger/commit/ca4a6428b127d5092e1409b9dad1697276d74c3c]
 

> setup CI using Github action
> 
>
> Key: RANGER-4072
> URL: https://issues.apache.org/jira/browse/RANGER-4072
> Project: Ranger
>  Issue Type: Task
>  Components: build-infra
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: PR-216.diff, RANGER-4072.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ranger currently uses Travis for CI. Apache infra requires projects to 
> migrate away from Travis CI and suggests to use Github actins.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [ranger] kumaab merged pull request #216: RANGER-4072: Enable CI for ranger

[via GitHub]

kumaab merged PR #216:
URL: https://github.com/apache/ranger/pull/216


-- 
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] [Updated] (RANGER-4072) setup CI using Github action

[Abhishek Kumar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Kumar updated RANGER-4072:
---
Attachment: PR-216.diff

> setup CI using Github action
> 
>
> Key: RANGER-4072
> URL: https://issues.apache.org/jira/browse/RANGER-4072
> Project: Ranger
>  Issue Type: Task
>  Components: build-infra
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: PR-216.diff, RANGER-4072.patch
>
>
> Ranger currently uses Travis for CI. Apache infra requires projects to 
> migrate away from Travis CI and suggests to use Github actins.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4072) setup CI using Github action

[Abhishek Kumar (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689369#comment-17689369
 ] 

Abhishek Kumar commented on RANGER-4072:


Changes are tracked here: [https://github.com/apache/ranger/pull/216]

 

> setup CI using Github action
> 
>
> Key: RANGER-4072
> URL: https://issues.apache.org/jira/browse/RANGER-4072
> Project: Ranger
>  Issue Type: Task
>  Components: build-infra
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: PR-216.diff, RANGER-4072.patch
>
>
> Ranger currently uses Travis for CI. Apache infra requires projects to 
> migrate away from Travis CI and suggests to use Github actins.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74308: RANGER-3999: Implement more efficient way to handle _any access authorization - Part 3

[Abhay Kulkarni]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74308/
---

Review request for ranger, madhan and Madhan Neethiraj.


Bugs: RANGER-3999
https://issues.apache.org/jira/browse/RANGER-3999


Repository: ranger


Description
---

When ANY_ACCESS is requested, the policy matching algorithm returns match if 
match-type is not NONE. However, the current check for ANY_ACCESS checks not 
only the request's access-type but also the value in the request's context. As 
the request's context's attribute ISANYACCESS may be set up for processing any 
of the multiple accesses specified in the context's ACCESSTYPES attribute, only 
request's access-type needs to be checked to determine if the policy matches.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
 9a0df550c 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerAccessRequestUtil.java
 a51f2322a 


Diff: https://reviews.apache.org/r/74308/diff/1/


Testing
---

Compiles clean and passes all unit tests.


Thanks,

Abhay Kulkarni

[GitHub] [ranger] mneethiraj commented on pull request #216: Enable CI for ranger

[via GitHub]

mneethiraj commented on PR #216:
URL: https://github.com/apache/ranger/pull/216#issuecomment-1431968236

   @kumaab  - thanks for the patch to enable CI. Please file a RANGER jira and 
push this commit; you can also consider using RANGER-4072 for this commit.


-- 
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] [Assigned] (RANGER-4085) Search filter hint is not available where you search for policy

[Abhishek (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek reassigned RANGER-4085:


Assignee: Abhishek  (was: Brijesh Bhalala)

> Search filter hint is not available where you search for policy
> ---
>
> Key: RANGER-4085
> URL: https://issues.apache.org/jira/browse/RANGER-4085
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Abhishek
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.34.33 PM.png
>
>
> Search filter hint is not available where you search for policy
> Verify with old ranger UI we had i icon had hints 
> eg below for hadoop sql
> {code:java}
> Search Filter HintsWildcard searches ( for example using * or ? ) are not 
> currently supported.Group Name : Name of Group.Policy Name : Enter name of 
> policy.Status : Status of Policy Enable/Disable.User Name : Name of User.Role 
> Name : Name of Role.Policy Label : Label of policyHive Database : Hive 
> database.URL : Hive url.Hive Service : Hive ServiceGlobal : GlobalStorage 
> Type : Storage TypeHive Table : Table NameHive UDF : Hive udf.Storage URL : 
> Storage URLHive Column : Column Name {code}
> Actual : Search filter Hint is missing 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4091) Policy condition & Permission window should close by any click events

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4091:
---
Priority: Critical  (was: Major)

> Policy condition  & Permission window should close by any click events
> --
>
> Key: RANGER-4091
> URL: https://issues.apache.org/jira/browse/RANGER-4091
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Critical
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 9.14.47 PM.png
>
>
> Policy condition window Overlaps with Policy permisions window as Policy 
> condition  & Permission window is not closing by any click events
> Steps to reproduce :
> 1. Try to create any tag based policy 
> 2. Click on Policy condition + icon
> 3. Click on permission + icon
> Actual :  Policy condition  & Permission window is not closing by any click 
> events
> Expected :   Policy condition  & Permission window should close by any click 
> events



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4091) Policy condition & Permission window should close by any click events

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4091:
--

 Summary: Policy condition  & Permission window should close by any 
click events
 Key: RANGER-4091
 URL: https://issues.apache.org/jira/browse/RANGER-4091
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Anupam Rai
 Attachments: Screenshot 2023-02-15 at 9.14.47 PM.png

Policy condition window Overlaps with Policy permisions window as Policy 
condition  & Permission window is not closing by any click events

Steps to reproduce :

1. Try to create any tag based policy 
2. Click on Policy condition + icon
3. Click on permission + icon

Actual :  Policy condition  & Permission window is not closing by any click 
events

Expected :   Policy condition  & Permission window should close by any click 
events



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4091) Policy condition & Permission window should close by any click events

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4091:
---
Attachment: Screenshot 2023-02-15 at 9.14.47 PM.png

> Policy condition  & Permission window should close by any click events
> --
>
> Key: RANGER-4091
> URL: https://issues.apache.org/jira/browse/RANGER-4091
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 9.14.47 PM.png
>
>
> Policy condition window Overlaps with Policy permisions window as Policy 
> condition  & Permission window is not closing by any click events
> Steps to reproduce :
> 1. Try to create any tag based policy 
> 2. Click on Policy condition + icon
> 3. Click on permission + icon
> Actual :  Policy condition  & Permission window is not closing by any click 
> events
> Expected :   Policy condition  & Permission window should close by any click 
> events



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4091) Policy condition & Permission window should close by any click events

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4091:
---
Labels: ranger-react  (was: )

> Policy condition  & Permission window should close by any click events
> --
>
> Key: RANGER-4091
> URL: https://issues.apache.org/jira/browse/RANGER-4091
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 9.14.47 PM.png
>
>
> Policy condition window Overlaps with Policy permisions window as Policy 
> condition  & Permission window is not closing by any click events
> Steps to reproduce :
> 1. Try to create any tag based policy 
> 2. Click on Policy condition + icon
> 3. Click on permission + icon
> Actual :  Policy condition  & Permission window is not closing by any click 
> events
> Expected :   Policy condition  & Permission window should close by any click 
> events



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4084) Login id which is available on left most corner coming as Camel case

[Abhishek (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek reassigned RANGER-4084:


Assignee: Abhishek  (was: Brijesh Bhalala)

> Login id which is available on left most corner coming as Camel case 
> -
>
> Key: RANGER-4084
> URL: https://issues.apache.org/jira/browse/RANGER-4084
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Abhishek
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.23.22 PM.png
>
>
> Login id which is available on left most corner coming as Camel case 
> Create user with 
> user name - lowercase 
> first name - lowercase 
> Still is username is displayed in camel case  on ranger banner , Screenshot 
> attached.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4090) Resouce lookup exception message is not available in react UI

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4090:
---

Assignee: Mugdha Varadkar

> 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: Mugdha Varadkar
>Priority: Major
>  Labels: ranger-react
>
> 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] [Assigned] (RANGER-4089) Getting browser specific pop-up message if try to delete policy after edit

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4089:
---

Assignee: Mugdha Varadkar

> Getting browser specific pop-up message if try to delete policy after edit 
> ---
>
> Key: RANGER-4089
> URL: https://issues.apache.org/jira/browse/RANGER-4089
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Mugdha Varadkar
>Priority: Critical
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 5.44.05 PM.png
>
>
> Getting browser specific pop-up message if try to delete policy after edit 
> Steps to reproduce :
> 1. Create a policy
> 2. Edit policy , instead of save click on delete , user is getting browser 
> specic pop-up .
> 3. If move to different tab Policy is deleted & user will be present on 
> Deleted policy edit page .
> Expected : Behaviour should be like old UI , Once system specific Delete 
> confirmation popup should be enough.
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4088:
---

Assignee: Dhaval Rajpara

> 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] [Assigned] (RANGER-4087) Loader is still loading for resource field for policy creation even after Resource lookup API gives 200/204

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4087:
---

Assignee: Dhaval Rajpara

> 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
>
> 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] [Assigned] (RANGER-4086) An admin user without permissions on all permission modules is able to view permissions module page and assign permissions to self

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4086:
---

Assignee: Dhaval Rajpara

> An admin user without permissions on all permission modules is able to view 
> permissions module page and assign permissions to self
> --
>
> Key: RANGER-4086
> URL: https://issues.apache.org/jira/browse/RANGER-4086
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Dhaval Rajpara
>Priority: Major
>
> On the Ranger UI, create a new admin user and login as the newly created user 
> in a different browser.
> Then remove the permissions for the user on any module.
> In the second browser, the newly created user is still able to access the 
> permissions module page and is able to assign permissions to self.
> Ideally, if a user does not have access to all the permission modules, then 
> the user should not be able to edit permissions, 
> or if a user tries to remove permissions for an admin user, it should result 
> in an error or a notification stating that permissions for admin users can't 
> be removed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4084) Login id which is available on left most corner coming as Camel case

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4084:
---

Assignee: Brijesh Bhalala

> Login id which is available on left most corner coming as Camel case 
> -
>
> Key: RANGER-4084
> URL: https://issues.apache.org/jira/browse/RANGER-4084
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.23.22 PM.png
>
>
> Login id which is available on left most corner coming as Camel case 
> Create user with 
> user name - lowercase 
> first name - lowercase 
> Still is username is displayed in camel case  on ranger banner , Screenshot 
> attached.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4085) Search filter hint is not available where you search for policy

[Mugdha Varadkar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar reassigned RANGER-4085:
---

Assignee: Brijesh Bhalala

> Search filter hint is not available where you search for policy
> ---
>
> Key: RANGER-4085
> URL: https://issues.apache.org/jira/browse/RANGER-4085
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.34.33 PM.png
>
>
> Search filter hint is not available where you search for policy
> Verify with old ranger UI we had i icon had hints 
> eg below for hadoop sql
> {code:java}
> Search Filter HintsWildcard searches ( for example using * or ? ) are not 
> currently supported.Group Name : Name of Group.Policy Name : Enter name of 
> policy.Status : Status of Policy Enable/Disable.User Name : Name of User.Role 
> Name : Name of Role.Policy Label : Label of policyHive Database : Hive 
> database.URL : Hive url.Hive Service : Hive ServiceGlobal : GlobalStorage 
> Type : Storage TypeHive Table : Table NameHive UDF : Hive udf.Storage URL : 
> Storage URLHive Column : Column Name {code}
> Actual : Search filter Hint is missing 



--
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

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4090:
---
Labels: ranger-react  (was: )

> 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
>Priority: Major
>  Labels: ranger-react
>
> 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] [Created] (RANGER-4090) Resouce lookup exception message is not available in react UI

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4090:
--

 Summary: 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


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-4089) Getting browser specific pop-up message if try to delete policy after edit

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4089:
---
Attachment: Screenshot 2023-02-15 at 5.44.05 PM.png

> Getting browser specific pop-up message if try to delete policy after edit 
> ---
>
> Key: RANGER-4089
> URL: https://issues.apache.org/jira/browse/RANGER-4089
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Critical
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 5.44.05 PM.png
>
>
> Getting browser specific pop-up message if try to delete policy after edit 
> Steps to reproduce :
> 1. Create a policy
> 2. Edit policy , instead of save click on delete , user is getting browser 
> specic pop-up .
> 3. If move to different tab Policy is deleted & user will be present on 
> Deleted policy edit page .
> Expected : Behaviour should be like old UI , Once system specific Delete 
> confirmation popup should be enough.
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4089) Getting browser specific pop-up message if try to delete policy after edit

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4089:
--

 Summary: Getting browser specific pop-up message if try to delete 
policy after edit 
 Key: RANGER-4089
 URL: https://issues.apache.org/jira/browse/RANGER-4089
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Anupam Rai


Getting browser specific pop-up message if try to delete policy after edit 

Steps to reproduce :
1. Create a policy
2. Edit policy , instead of save click on delete , user is getting browser 
specic pop-up .
3. If move to different tab Policy is deleted & user will be present on Deleted 
policy edit page .

Expected : Behaviour should be like old UI , Once system specific Delete 
confirmation popup should be enough.

Thanks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4089) Getting browser specific pop-up message if try to delete policy after edit

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4089:
---
Labels: ranger-react  (was: )

> Getting browser specific pop-up message if try to delete policy after edit 
> ---
>
> Key: RANGER-4089
> URL: https://issues.apache.org/jira/browse/RANGER-4089
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Critical
>  Labels: ranger-react
>
> Getting browser specific pop-up message if try to delete policy after edit 
> Steps to reproduce :
> 1. Create a policy
> 2. Edit policy , instead of save click on delete , user is getting browser 
> specic pop-up .
> 3. If move to different tab Policy is deleted & user will be present on 
> Deleted policy edit page .
> Expected : Behaviour should be like old UI , Once system specific Delete 
> confirmation popup should be enough.
> 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

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4088:
---
Labels: ranger-react  (was: )

> 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
>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] [Created] (RANGER-4088) While editing policy All permissions & and other resource fields are getting disappered

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4088:
--

 Summary: 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
 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

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4088:
---
Attachment: Screenshot 2023-02-15 at 4.51.18 PM.png

> 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
>Priority: Critical
> 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-4086) An admin user without permissions on all permission modules is able to view permissions module page and assign permissions to self

[Abhishek (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek updated RANGER-4086:
-
Description: 
On the Ranger UI, create a new admin user and login as the newly created user 
in a different browser.
Then remove the permissions for the user on any module.
In the second browser, the newly created user is still able to access the 
permissions module page and is able to assign permissions to self.
Ideally, if a user does not have access to all the permission modules, then the 
user should not be able to edit permissions, 
or if a user tries to remove permissions for an admin user, it should result in 
an error or a notification stating that permissions for admin users can't be 
removed

  was:
On the Ranger UI, create a new admin user and login as the newly created user 
in a different browser.
Then remove the permissions for the user on any module.
In the second browser, the newly created user is still able to access the 
permissions module page and is able to assign permissions to self.
Ideally, if a user does not have access to all the permission modules, then the 
user should not be able to edit permissions.


> An admin user without permissions on all permission modules is able to view 
> permissions module page and assign permissions to self
> --
>
> Key: RANGER-4086
> URL: https://issues.apache.org/jira/browse/RANGER-4086
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Priority: Major
>
> On the Ranger UI, create a new admin user and login as the newly created user 
> in a different browser.
> Then remove the permissions for the user on any module.
> In the second browser, the newly created user is still able to access the 
> permissions module page and is able to assign permissions to self.
> Ideally, if a user does not have access to all the permission modules, then 
> the user should not be able to edit permissions, 
> or if a user tries to remove permissions for an admin user, it should result 
> in an error or a notification stating that permissions for admin users can't 
> be removed



--
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

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4087:
---
Labels: ranger-react  (was: )

> 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
>Priority: Major
>  Labels: ranger-react
>
> 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] [Created] (RANGER-4087) Loader is still loading for resource field for policy creation even after Resource lookup API gives 200/204

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4087:
--

 Summary: 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


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] [Updated] (RANGER-4085) Search filter hint is not available where you search for policy

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4085:
---
Description: 
Search filter hint is not available where you search for policy

Verify with old ranger UI we had i icon had hints 

eg below for hadoop sql


{code:java}
Search Filter HintsWildcard searches ( for example using * or ? ) are not 
currently supported.Group Name : Name of Group.Policy Name : Enter name of 
policy.Status : Status of Policy Enable/Disable.User Name : Name of User.Role 
Name : Name of Role.Policy Label : Label of policyHive Database : Hive 
database.URL : Hive url.Hive Service : Hive ServiceGlobal : GlobalStorage Type 
: Storage TypeHive Table : Table NameHive UDF : Hive udf.Storage URL : Storage 
URLHive Column : Column Name {code}

Actual : Search filter Hint is missing 

  was:Search filter hint is not available where you search for policy


> Search filter hint is not available where you search for policy
> ---
>
> Key: RANGER-4085
> URL: https://issues.apache.org/jira/browse/RANGER-4085
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.34.33 PM.png
>
>
> Search filter hint is not available where you search for policy
> Verify with old ranger UI we had i icon had hints 
> eg below for hadoop sql
> {code:java}
> Search Filter HintsWildcard searches ( for example using * or ? ) are not 
> currently supported.Group Name : Name of Group.Policy Name : Enter name of 
> policy.Status : Status of Policy Enable/Disable.User Name : Name of User.Role 
> Name : Name of Role.Policy Label : Label of policyHive Database : Hive 
> database.URL : Hive url.Hive Service : Hive ServiceGlobal : GlobalStorage 
> Type : Storage TypeHive Table : Table NameHive UDF : Hive udf.Storage URL : 
> Storage URLHive Column : Column Name {code}
> Actual : Search filter Hint is missing 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4085) Search filter hint is not available where you search for policy

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4085:
---
Attachment: Screenshot 2023-02-15 at 4.34.33 PM.png

> Search filter hint is not available where you search for policy
> ---
>
> Key: RANGER-4085
> URL: https://issues.apache.org/jira/browse/RANGER-4085
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.34.33 PM.png
>
>
> Search filter hint is not available where you search for policy



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4086) An admin user without permissions on all permission modules is able to view permissions module page and assign permissions to self

[Abhishek (Jira)]

Abhishek created RANGER-4086:


 Summary: An admin user without permissions on all permission 
modules is able to view permissions module page and assign permissions to self
 Key: RANGER-4086
 URL: https://issues.apache.org/jira/browse/RANGER-4086
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Abhishek


On the Ranger UI, create a new admin user and login as the newly created user 
in a different browser.
Then remove the permissions for the user on any module.
In the second browser, the newly created user is still able to access the 
permissions module page and is able to assign permissions to self.
Ideally, if a user does not have access to all the permission modules, then the 
user should not be able to edit permissions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4085) Search filter hint is not available where you search for policy

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4085:
---
Labels: ranger-react  (was: )

> Search filter hint is not available where you search for policy
> ---
>
> Key: RANGER-4085
> URL: https://issues.apache.org/jira/browse/RANGER-4085
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
>
> Search filter hint is not available where you search for policy



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4084) Login id which is available on left most corner coming as Camel case

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4084:
---
Description: 
Login id which is available on left most corner coming as Camel case 

Create user with 
user name - lowercase 
first name - lowercase 


Still is username is displayed in camel case  on ranger banner , Screenshot 
attached.

  was:Login id which is available on left most corner coming as Camel case 


> Login id which is available on left most corner coming as Camel case 
> -
>
> Key: RANGER-4084
> URL: https://issues.apache.org/jira/browse/RANGER-4084
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.23.22 PM.png
>
>
> Login id which is available on left most corner coming as Camel case 
> Create user with 
> user name - lowercase 
> first name - lowercase 
> Still is username is displayed in camel case  on ranger banner , Screenshot 
> attached.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4085) Search filter hint is not available where you search for policy

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4085:
--

 Summary: Search filter hint is not available where you search for 
policy
 Key: RANGER-4085
 URL: https://issues.apache.org/jira/browse/RANGER-4085
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Anupam Rai


Search filter hint is not available where you search for policy



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4084) Login id which is available on left most corner coming as Camel case

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4084:
---
Labels: ranger-react  (was: )

> Login id which is available on left most corner coming as Camel case 
> -
>
> Key: RANGER-4084
> URL: https://issues.apache.org/jira/browse/RANGER-4084
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.23.22 PM.png
>
>
> Login id which is available on left most corner coming as Camel case 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4084) Login id which is available on left most corner coming as Camel case

[Anupam Rai (Jira)]

Anupam Rai created RANGER-4084:
--

 Summary: Login id which is available on left most corner coming as 
Camel case 
 Key: RANGER-4084
 URL: https://issues.apache.org/jira/browse/RANGER-4084
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Anupam Rai
 Attachments: Screenshot 2023-02-15 at 4.23.22 PM.png

Login id which is available on left most corner coming as Camel case 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4084) Login id which is available on left most corner coming as Camel case

[Anupam Rai (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anupam Rai updated RANGER-4084:
---
Attachment: Screenshot 2023-02-15 at 4.23.22 PM.png

> Login id which is available on left most corner coming as Camel case 
> -
>
> Key: RANGER-4084
> URL: https://issues.apache.org/jira/browse/RANGER-4084
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>  Labels: ranger-react
> Attachments: Screenshot 2023-02-15 at 4.23.22 PM.png
>
>
> Login id which is available on left most corner coming as Camel case 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)