[jira] [Assigned] (RANGER-4383) In Audit, Plugin Status tab if the record of respective service is in second page then Service Type filter for that service would show no result
[ https://issues.apache.org/jira/browse/RANGER-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala reassigned RANGER-4383: --- Assignee: Brijesh Bhalala (was: Dhaval Rajpara) > In Audit, Plugin Status tab if the record of respective service is in second > page then Service Type filter for that service would show no result > > > Key: RANGER-4383 > URL: https://issues.apache.org/jira/browse/RANGER-4383 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Minor > Labels: ranger-react > > In Audit, Plugin Status tab if the records of respective service for eg KMS > is in second page then Service Type filter for that service would show no > result. > Workaround is using Service Name filter. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4381) [Ranger React UI] Difference in user lookup API request in permissions module page between React UI and BackBone UI
[ https://issues.apache.org/jira/browse/RANGER-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4381: Attachment: 0001-RANGER-4381.patch > [Ranger React UI] Difference in user lookup API request in permissions module > page between React UI and BackBone UI > --- > > Key: RANGER-4381 > URL: https://issues.apache.org/jira/browse/RANGER-4381 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4381.patch > > > In Ranger backbone UI, when trying to add users to a particular permissions > module, > when typing the user name, the user lookup is done only for users who are > visible. > In React UI, the lookup is not being restricted to visible users. > Ideally, if a user is hidden, it would mean that the user is deleted from the > source, > and in such scenarios, the users must not be listed for user lookups. > This is a regression from the previous UI behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4304) Update swagger version in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4304: Summary: Update swagger version in Ranger (was: Update swagger version in the website) > Update swagger version in Ranger > > > Key: RANGER-4304 > URL: https://issues.apache.org/jira/browse/RANGER-4304 > Project: Ranger > Issue Type: Improvement > Components: documentation >Reporter: Arnout Engelen >Assignee: Mugdha Varadkar >Priority: Major > > The Ranger website embeds a Swagger UI, AFAICS currently version 2.2.10. > Older versions of swagger, such as this one, suffer from a number of security > weaknesses. > > While fortunately [https://ranger.apache.org|https://ranger.apache.org/] does > not have any sensitive cookies or login mechanism or similar, so there isn't > really anything to compromise, it would be good to update to a recent version > of Swagger. Could you look into that? > > It is somewhat unclear to me whether the ranger site is maintained in SVN > ([https://svn.apache.org/viewvc/ranger/site/)] or git > ([https://github.com/apache/ranger-site]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4319) Restricting policy name character to configurable length
[ https://issues.apache.org/jira/browse/RANGER-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Gupta resolved RANGER-4319. -- Resolution: Fixed > Restricting policy name character to configurable length > > > Key: RANGER-4319 > URL: https://issues.apache.org/jira/browse/RANGER-4319 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Rakesh Gupta >Assignee: Rakesh Gupta >Priority: Major > Attachments: > 0001-RANGER-4319-Restricting-policy-name-character-to-con.patch > > > while creating a policy, policy-name should not be greater than 255 > characters(by default), > it can be configured using below param. > * ranger.policyname.maxlength > This will be flag base implementation (for backward compatibility) and by > default flag will be enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4319) Restricting policy name character to configurable length
[ https://issues.apache.org/jira/browse/RANGER-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Gupta updated RANGER-4319: - Fix Version/s: 3.0.0 > Restricting policy name character to configurable length > > > Key: RANGER-4319 > URL: https://issues.apache.org/jira/browse/RANGER-4319 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Rakesh Gupta >Assignee: Rakesh Gupta >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4319-Restricting-policy-name-character-to-con.patch > > > while creating a policy, policy-name should not be greater than 255 > characters(by default), > it can be configured using below param. > * ranger.policyname.maxlength > This will be flag base implementation (for backward compatibility) and by > default flag will be enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4319) Restricting policy name character to configurable length
[ https://issues.apache.org/jira/browse/RANGER-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760717#comment-17760717 ] Rakesh Gupta commented on RANGER-4319: -- Apache commit : https://github.com/apache/ranger/commit/5f8e3c1b7572d842f19a045dde6ed44209246806 > Restricting policy name character to configurable length > > > Key: RANGER-4319 > URL: https://issues.apache.org/jira/browse/RANGER-4319 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Rakesh Gupta >Assignee: Rakesh Gupta >Priority: Major > Attachments: > 0001-RANGER-4319-Restricting-policy-name-character-to-con.patch > > > while creating a policy, policy-name should not be greater than 255 > characters(by default), > it can be configured using below param. > * ranger.policyname.maxlength > This will be flag base implementation (for backward compatibility) and by > default flag will be enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74576: RANGER-4387: optimized loading of userstore from the database
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74576/#review225710
---
Ship it!
Ship It!
- Pradeep Agrawal
On Aug. 31, 2023, 12:47 a.m., Madhan Neethiraj wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74576/
> ---
>
> (Updated Aug. 31, 2023, 12:47 a.m.)
>
>
> Review request for ranger, Abhay Kulkarni, Mehul Parikh, Monika Kachhadiya,
> Pradeep Agrawal, Ramesh Mani, and Subhrat Chaudhary.
>
>
> Bugs: RANGER-4387
> https://issues.apache.org/jira/browse/RANGER-4387
>
>
> Repository: ranger
>
>
> Description
> ---
>
> - updated userstore cache loader to get only necessary columns from the
> database, instead entire XXUser and XXGroup JPA object
>
>
> Diffs
> -
>
> security-admin/src/main/java/org/apache/ranger/db/XXGroupDao.java 08e96f839
> security-admin/src/main/java/org/apache/ranger/db/XXUserDao.java 283d84fe1
>
> security-admin/src/main/java/org/apache/ranger/service/XGroupServiceBase.java
> 5404eab38
>
> security-admin/src/main/java/org/apache/ranger/service/XUserServiceBase.java
> 2fe54a919
> security-admin/src/main/resources/META-INF/jpa_named_queries.xml 3718b051a
>
>
> Diff: https://reviews.apache.org/r/74576/diff/1/
>
>
> Testing
> ---
>
> - verified that all existing tests pass successfully
> - verified that userstore returned by REST API
> service/xusers/download/{serviceName} remains same
>
>
> Thanks,
>
> Madhan Neethiraj
>
>
[jira] [Updated] (RANGER-4387) optimize loading of userstore from the database
[ https://issues.apache.org/jira/browse/RANGER-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-4387: - Attachment: RANGER-4387.patch > optimize loading of userstore from the database > --- > > Key: RANGER-4387 > URL: https://issues.apache.org/jira/browse/RANGER-4387 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4387.patch > > > While populating userstore, Ranger admin loads all XXUser and XXGroup objects > from the database. In deployments having large number of users/groups, > loading large number of JPA objects can add significant overheads. This > overhead can be avoided by loading only necessary attributes from the > database. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74576: RANGER-4387: optimized loading of userstore from the database
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74576/
---
Review request for ranger, Abhay Kulkarni, Mehul Parikh, Monika Kachhadiya,
Pradeep Agrawal, Ramesh Mani, and Subhrat Chaudhary.
Bugs: RANGER-4387
https://issues.apache.org/jira/browse/RANGER-4387
Repository: ranger
Description
---
- updated userstore cache loader to get only necessary columns from the
database, instead entire XXUser and XXGroup JPA object
Diffs
-
security-admin/src/main/java/org/apache/ranger/db/XXGroupDao.java 08e96f839
security-admin/src/main/java/org/apache/ranger/db/XXUserDao.java 283d84fe1
security-admin/src/main/java/org/apache/ranger/service/XGroupServiceBase.java
5404eab38
security-admin/src/main/java/org/apache/ranger/service/XUserServiceBase.java
2fe54a919
security-admin/src/main/resources/META-INF/jpa_named_queries.xml 3718b051a
Diff: https://reviews.apache.org/r/74576/diff/1/
Testing
---
- verified that all existing tests pass successfully
- verified that userstore returned by REST API
service/xusers/download/{serviceName} remains same
Thanks,
Madhan Neethiraj
[jira] [Created] (RANGER-4387) optimize loading of userstore from the database
Madhan Neethiraj created RANGER-4387: Summary: optimize loading of userstore from the database Key: RANGER-4387 URL: https://issues.apache.org/jira/browse/RANGER-4387 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj While populating userstore, Ranger admin loads all XXUser and XXGroup objects from the database. In deployments having large number of users/groups, loading large number of JPA objects can add significant overheads. This overhead can be avoided by loading only necessary attributes from the database. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4357) Enabling ORC audit for hdfs destination should not require 2 separate configurations
[ https://issues.apache.org/jira/browse/RANGER-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fateh Singh resolved RANGER-4357. - Resolution: Fixed Pull request merged https://github.com/apache/ranger/pull/279 > Enabling ORC audit for hdfs destination should not require 2 separate > configurations > > > Key: RANGER-4357 > URL: https://issues.apache.org/jira/browse/RANGER-4357 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Fateh Singh >Assignee: Fateh Singh >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently there are 2 configs which will be required to enable orc i.e. > xasecure.audit.destination.hdfs.batch.filequeue.filetype=orc and config > xasecure.audit.destination.hdfs.filetype=orc > Ideally, we would want only 1 config to enable orc > xasecure.audit.destination.hdfs.batch.filequeue.filetype=orc. Also, orc can > only be enabled from filequeue, so above config seems more reasonable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] rameeshm merged pull request #279: RANGER-4357: Consolidate configs required to enable ORC audit logs
rameeshm merged PR #279: URL: https://github.com/apache/ranger/pull/279 -- 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-4371) Ranger authn - add doAs support for JWT authentication
[ https://issues.apache.org/jira/browse/RANGER-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760383#comment-17760383 ] Dineshkumar Yadav commented on RANGER-4371: --- apache commit : https://github.com/apache/ranger/commit/5bc3cb303e1100e25e7b45df1407b250e662bc77 > Ranger authn - add doAs support for JWT authentication > -- > > Key: RANGER-4371 > URL: https://issues.apache.org/jira/browse/RANGER-4371 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > add doAs support for JWT based authentication -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74554: RANGER-4371: Ranger authn - add doAs support for JWT authentication
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74554/#review225709 --- Ship it! Ship It! - Mehul Parikh On Aug. 21, 2023, 4:21 p.m., Kishor Gollapalliwar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74554/ > --- > > (Updated Aug. 21, 2023, 4:21 p.m.) > > > Review request for ranger, Dineshkumar Yadav, Abhay Kulkarni, Madhan > Neethiraj, Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan > Periasamy. > > > Bugs: RANGER-4371 > https://issues.apache.org/jira/browse/RANGER-4371 > > > Repository: ranger > > > Description > --- > > add doAs support for JWT based authentication > > > Diffs > - > > > ranger-authn/src/main/java/org/apache/ranger/authz/handler/jwt/RangerDefaultJwtAuthHandler.java > c0d5b8d9a > > ranger-authn/src/main/java/org/apache/ranger/authz/handler/jwt/RangerJwtAuthHandler.java > 0973b42de > > > Diff: https://reviews.apache.org/r/74554/diff/1/ > > > Testing > --- > > 1. mvn clean compile package install > 2. User JWT authentication without doAs > 3. User JWT authentication with doAs > > > Thanks, > > Kishor Gollapalliwar > >
[jira] [Resolved] (RANGER-4290) Adding uiHint attribute in policy condition
[ https://issues.apache.org/jira/browse/RANGER-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar resolved RANGER-4290. --- Resolution: Fixed > Adding uiHint attribute in policy condition > --- > > Key: RANGER-4290 > URL: https://issues.apache.org/jira/browse/RANGER-4290 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4290.patch > > > RANGER-4157 introduced addition of Policy conditions to all service-defs. > However, this update does not include uiHint attribute in policy condition. > This needs to be fixed so that uiHint attribute will be available in all > service-defs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4285) Ranger Java Patch for adding uiHint in policy condition for upgrade scenario
[ https://issues.apache.org/jira/browse/RANGER-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar resolved RANGER-4285. --- Resolution: Fixed > Ranger Java Patch for adding uiHint in policy condition for upgrade scenario > > > Key: RANGER-4285 > URL: https://issues.apache.org/jira/browse/RANGER-4285 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4285.patch > > > Ranger Java Patch for adding uiHint in policy condition for upgrade scenario -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74575: RANGER-4285: Ranger Java Patch for adding uiHint in policy condition for upgrade scenario
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74575/#review225708 --- Ship it! Ship It! - Mehul Parikh On Aug. 29, 2023, 12:03 p.m., sanket shelar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74575/ > --- > > (Updated Aug. 29, 2023, 12:03 p.m.) > > > Review request for ranger, dinesh akhand, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4285 > https://issues.apache.org/jira/browse/RANGER-4285 > > > Repository: ranger > > > Description > --- > > Ranger Java Patch for adding uiHint in policy condition for upgrade scenario > > > Diffs > - > > security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql > a3b05d851 > security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql > 91ec963ed > security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql > 97eeea6ff > > security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql > cbae01f82 > security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql > 583464890 > > security-admin/src/main/java/org/apache/ranger/patch/PatchForAllServiceDefForPolicyConditionUpdate_J10057.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/74575/diff/1/ > > > Testing > --- > > Tested upgrade scenarios for all DB flavours. > > > Thanks, > > sanket shelar > >
[jira] [Resolved] (RANGER-4343) Atlas default policy is showing 2 "admin" users in policy items
[ https://issues.apache.org/jira/browse/RANGER-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar resolved RANGER-4343. --- Resolution: Fixed > Atlas default policy is showing 2 "admin" users in policy items > --- > > Key: RANGER-4343 > URL: https://issues.apache.org/jira/browse/RANGER-4343 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4343.patch > > > If a new atlas servcice is created with admin as username then the Atlas > default policies created will show 2 "admin" users in policy items. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74575: RANGER-4285: Ranger Java Patch for adding uiHint in policy condition for upgrade scenario
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74575/#review225707 --- Ship it! Ship It! - Kishor Gollapalliwar On Aug. 29, 2023, 12:03 p.m., sanket shelar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74575/ > --- > > (Updated Aug. 29, 2023, 12:03 p.m.) > > > Review request for ranger, dinesh akhand, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4285 > https://issues.apache.org/jira/browse/RANGER-4285 > > > Repository: ranger > > > Description > --- > > Ranger Java Patch for adding uiHint in policy condition for upgrade scenario > > > Diffs > - > > security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql > a3b05d851 > security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql > 91ec963ed > security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql > 97eeea6ff > > security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql > cbae01f82 > security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql > 583464890 > > security-admin/src/main/java/org/apache/ranger/patch/PatchForAllServiceDefForPolicyConditionUpdate_J10057.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/74575/diff/1/ > > > Testing > --- > > Tested upgrade scenarios for all DB flavours. > > > Thanks, > > sanket shelar > >
[jira] [Updated] (RANGER-4384) ORC audit for hdfs destination is too slow
[ https://issues.apache.org/jira/browse/RANGER-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4384: - Description: ORC audit for hdfs destination is too slow when we generate 60GB audit in a day and audits are not being able to written from spool directories to HDFS due to slowness. Below Configurations are set on the test cluster: orc.buffersize=10mb orc.stripesize=10mb filespool.buffer.size=10k file.rollover.sec=1day xasecure.audit.provider.queue.size=1mb default CC: [~rmani] [~fateh288] was: ORC audit for hdfs destination is too slow when we generate 60GB audit in a day and due to slowness it started writing to spool directory. Even audits are not able flush from spool directories to HDFS due to slowness. Below Configurations are set on the test cluster: orc.buffersize=10mb orc.stripesize=10mb filespool.buffer.size=10k file.rollover.sec=1day xasecure.audit.provider.queue.size=1mb default CC: [~rmani] [~fateh288] > ORC audit for hdfs destination is too slow > -- > > Key: RANGER-4384 > URL: https://issues.apache.org/jira/browse/RANGER-4384 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.3.0, 2.4.0 >Reporter: Bhavik Patel >Priority: Major > > ORC audit for hdfs destination is too slow when we generate 60GB audit in a > day and audits are not being able to written from spool directories to HDFS > due to slowness. > Below Configurations are set on the test cluster: > orc.buffersize=10mb > orc.stripesize=10mb > filespool.buffer.size=10k > file.rollover.sec=1day > xasecure.audit.provider.queue.size=1mb default > > CC: [~rmani] [~fateh288] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4386) Latest usage documents
LiJie2023 created RANGER-4386: - Summary: Latest usage documents Key: RANGER-4386 URL: https://issues.apache.org/jira/browse/RANGER-4386 Project: Ranger Issue Type: Improvement Components: documentation Reporter: LiJie2023 Hello, our company is planning to use Ranger recently, but during the pre research process, we found that there are fewer documents and many of them are outdated. Of course, it is also possible that there is a problem with the way I obtained the documents. Do you have the latest documentation on usage and related concepts -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] IOrzo opened a new pull request, #280: RANGER-4385: Fix role filtering logic in RolePredicateUtil
IOrzo opened a new pull request, #280: URL: https://github.com/apache/ranger/pull/280 ## What changes were proposed in this pull request? Fix role filtering logic in RolePredicateUtil ## How was this patch tested? 1. Create a new user with role USER in Ranger Admin 2. Create a role like this table |Role Name|Users|Groups|Roles| |-|-|-|-| |role_second|test|--|role_first| 3. use this account to query through the role name parameter role_first -- 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
Re: Review Request 74573: RANGER-4290: Adding uiHint attribute in policy condition
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74573/#review225706 --- Ship it! Ship It! - Mehul Parikh On Aug. 29, 2023, 10:57 a.m., sanket shelar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74573/ > --- > > (Updated Aug. 29, 2023, 10:57 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Sailaja > Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4290 > https://issues.apache.org/jira/browse/RANGER-4290 > > > Repository: ranger > > > Description > --- > > RANGER-4157 introduced addition of Policy conditions to all service-defs. > However, this update does not include uiHint attribute in policy condition. > This needs to be fixed so that uiHint attribute will be available in all > service-defs. > > > Diffs > - > > > security-admin/src/main/java/org/apache/ranger/service/RangerServiceDefServiceBase.java > 91d5f26bc > > > Diff: https://reviews.apache.org/r/74573/diff/1/ > > > Testing > --- > > Tested for service-defs and UiHint attribute is present in policy condition. > > > Thanks, > > sanket shelar > >
Re: Review Request 74574: RANGER-4343: Atlas default policy is showing 2 "admin" users in policy items
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74574/#review225705 --- Ship it! Ship It! - Mehul Parikh On Aug. 29, 2023, 11:59 a.m., sanket shelar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74574/ > --- > > (Updated Aug. 29, 2023, 11:59 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Sailaja > Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4343 > https://issues.apache.org/jira/browse/RANGER-4343 > > > Repository: ranger > > > Description > --- > > If a new atlas servcice is created with admin as username then the Atlas > default policies created will show 2 "admin" users in policy items. > > > Diffs > - > > > plugin-atlas/src/main/java/org/apache/ranger/services/atlas/RangerServiceAtlas.java > 626862698 > > > Diff: https://reviews.apache.org/r/74574/diff/1/ > > > Testing > --- > > Tested by creating new Atlas service with admin as username, unable to see > the issue. > > > Thanks, > > sanket shelar > >
[jira] [Created] (RANGER-4385) [Ranger UI] Querying role information by role name in the role management module does not display correct data
bing created RANGER-4385: Summary: [Ranger UI] Querying role information by role name in the role management module does not display correct data Key: RANGER-4385 URL: https://issues.apache.org/jira/browse/RANGER-4385 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.2.0 Reporter: bing Fix For: 2.2.0 there is a role data: |Role Name|Users|Groups|Roles| |role_second|test|–|role_first| When I use a common user account to query through the role name parameter role_first, this piece of data is not displayed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
