Re: Review Request 74487: RANGER-4293: Long User/group/role name overflowing from delete confirmation dialog box
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74487/#review225567 --- Ship it! Ship It! - Mugdha Varadkar On June 22, 2023, 12:15 p.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74487/ > --- > > (Updated June 22, 2023, 12:15 p.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4293 > https://issues.apache.org/jira/browse/RANGER-4293 > > > Repository: ranger > > > Description > --- > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > > Steps to reproduce: > > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdg > fdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/styles/style.css c8d4dcc4b > security-admin/src/main/webapp/react-webapp/src/views/CustomBreadcrumb.jsx > e3ba45f0e > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx > b77c0fe73 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx > 86059c463 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx > 4e1fc9205 > > > Diff: https://reviews.apache.org/r/74487/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)Verified the following things:- > 1)CRUD Operation in user/group/role module. > 2)user/group/role listing pages. > > > Thanks, > > Brijesh Bhalala > >
[jira] [Commented] (RANGER-4286) allow security-zone to exist without any services/resources assigned yet
[
https://issues.apache.org/jira/browse/RANGER-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736330#comment-17736330
]
Madhan Neethiraj commented on RANGER-4286:
--
{noformat}
commit 7a7a78720284b29acb2757f3949b751c1bc8eceb (origin/master, origin/HEAD)
Author: Madhan Neethiraj
Date: Thu Jun 22 17:39:57 2023 -0700
RANGER-4286: allow security-zone to exist without any services/resources
assigned - #2
{noformat}
> allow security-zone to exist without any services/resources assigned yet
>
>
> Key: RANGER-4286
> URL: https://issues.apache.org/jira/browse/RANGER-4286
> Project: Ranger
> Issue Type: Improvement
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
>
> Currently, Ranger requires a security-zone to have at lease one service with
> at least one resource. Often, admins would like to create a number of
> security-zones first (like prod, stage, test, finance, mktg, business-unit-1,
> business-unit-2) and later add services/resources to these zones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4299) Zone resource validator handling of resources at different levels
[
https://issues.apache.org/jira/browse/RANGER-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-4299:
-
Attachment: RANGER-4299.patch
> Zone resource validator handling of resources at different levels
> -
>
> Key: RANGER-4299
> URL: https://issues.apache.org/jira/browse/RANGER-4299
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: RANGER-4299.patch
>
>
> A critical requirement for security zone is to ensure that a given resource
> belongs to at most only one security zone. This works well when all zones
> have resources with the same resource hierarchy - like path, database/table,
> database/table. However, when zones contain resources with different
> hierarchies, the validation doesn't enforce above requirement. For example:
>
>
> {code:java}
> Zone1: [ { database: db1 } ]
> Zone2: [ { database: db1, table: tbl1 } ]
> {code}
>
> Above zones are not a valid, as table {{db1.tbl1}} belongs to both Zone1 and
> Zone2. However, zone resource validator doesn't handle this case correctly
> hence allows zones with above resources. Validation should be fixed to
> prevent zones with above resources.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74490: RANGER-4299: fixed security-zone validator to handle resources at different hierarchies
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74490/ --- Review request for ranger, Ankita Sinha, Abhay Kulkarni, Ramesh Mani, Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy. Bugs: RANGER-4299 https://issues.apache.org/jira/browse/RANGER-4299 Repository: ranger Description --- In trie objects built during security zone validation, child level tries don't get inherited evaluators which resulted in incorrect validation. Fixed trie creation to ensure that inherited evaluators from parent levels would be included. Diffs - agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerSecurityZoneValidator.java 1a2b3160b agents-common/src/test/java/org/apache/ranger/plugin/model/validation/RangerSecurityZoneValidatorTest.java ef95c69aa Diff: https://reviews.apache.org/r/74490/diff/1/ Testing --- - added test case to cover two zones having resources with differnt hierarchies - verified that existing tests pass successfully Thanks, Madhan Neethiraj
[jira] [Created] (RANGER-4299) Zone resource validator handling of resources at different levels
Madhan Neethiraj created RANGER-4299:
Summary: Zone resource validator handling of resources at
different levels
Key: RANGER-4299
URL: https://issues.apache.org/jira/browse/RANGER-4299
Project: Ranger
Issue Type: Bug
Components: admin
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
A critical requirement for security zone is to ensure that a given resource
belongs to at most only one security zone. This works well when all zones have
resources with the same resource hierarchy - like path, database/table,
database/table. However, when zones contain resources with different
hierarchies, the validation doesn't enforce above requirement. For example:
{code:java}
Zone1: [ { database: db1 } ]
Zone2: [ { database: db1, table: tbl1 } ]
{code}
Above zones are not a valid, as table {{db1.tbl1}} belongs to both Zone1 and
Zone2. However, zone resource validator doesn't handle this case correctly
hence allows zones with above resources. Validation should be fixed to prevent
zones with above resources.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4298) Multi-threaded tagsync needed
[ https://issues.apache.org/jira/browse/RANGER-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Eckman updated RANGER-4298: --- Description: We are in the process of migrating our entire large data lakes (S3, MinIO) from resource-based to tag-based AC. This migration is phased and estimated to continue through Q3. In this phase we need to import 250K tags into Ranger from Apache Atlas. At the current, single-threaded rate of 500ms/tag, this will take 6 to 7 days. Beyond this migration, we expect to be incorporating multiple external datasets into our datalakes at regular intervals, which will cause roughly the same quantity of tags to be imported. So this is not a one-time thing, it is expected to recur. It would be great if tagsync could be made multi-threaded. was: We are in the process of migrating our entire large data lakes (S3, MinIO) from resource-based to tag-based AC. This migration is phased and estimated to continue through Q3. In this phase we need to import 250K tags into Ranger from Apache Atlas. At the current, single-threaded rate of 500ms/tag, this will take 6 to 7 days. Beyond this migration, we expect to be incorporating multiple external datasets into our datalakes, which will cause roughly the same quantity of tags to be imported. So this is not a one-time thing, it is expected to recur. It would be great if tagsync could be made multi-threaded. > Multi-threaded tagsync needed > - > > Key: RANGER-4298 > URL: https://issues.apache.org/jira/browse/RANGER-4298 > Project: Ranger > Issue Type: Improvement > Components: Ranger, tagsync >Reporter: Barbara Eckman >Priority: Major > > We are in the process of migrating our entire large data lakes (S3, MinIO) > from resource-based to tag-based AC. This migration is phased and estimated > to continue through Q3. In this phase we need to import 250K tags into > Ranger from Apache Atlas. At the current, single-threaded rate of 500ms/tag, > this will take 6 to 7 days. > Beyond this migration, we expect to be incorporating multiple external > datasets into our datalakes at regular intervals, which will cause roughly > the same quantity of tags to be imported. > So this is not a one-time thing, it is expected to recur. It would be great > if tagsync could be made multi-threaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4298) Multi-threaded tagsync needed
Barbara Eckman created RANGER-4298: -- Summary: Multi-threaded tagsync needed Key: RANGER-4298 URL: https://issues.apache.org/jira/browse/RANGER-4298 Project: Ranger Issue Type: Improvement Components: Ranger, tagsync Reporter: Barbara Eckman We are in the process of migrating our entire large data lakes (S3, MinIO) from resource-based to tag-based AC. This migration is phased and estimated to continue through Q3. In this phase we need to import 250K tags into Ranger from Apache Atlas. At the current, single-threaded rate of 500ms/tag, this will take 6 to 7 days. Beyond this migration, we expect to be incorporating multiple external datasets into our datalakes, which will cause roughly the same quantity of tags to be imported. So this is not a one-time thing, it is expected to recur. It would be great if tagsync could be made multi-threaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74488: RANGER-4292: Long zone names are not showing perfectly in the zone search dropdown of service manager
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74488/#review225566 --- Ship it! Ship It! - Mugdha Varadkar On June 22, 2023, 12:26 p.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74488/ > --- > > (Updated June 22, 2023, 12:26 p.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4292 > https://issues.apache.org/jira/browse/RANGER-4292 > > > Repository: ranger > > > Description > --- > > Extra white space gets added at the end of the zone search dropdown when a > long zone name is selected. > > Steps to reproduce: > > 1. create a long zone name like: > >"dffdgfdgfdgdfffdgdfgerfgregregergregregerger" > > 2. Click on the zone search bar on service manager and select the created > zone name. > > 3. Then again click on the search bar and horizontally scroll the search > dropdown. > > 4. There is a long white space added at the end as shown in attached ss. > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx > 05934e447 > security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx > 29b7c1ce9 > > > Diff: https://reviews.apache.org/r/74488/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)Verified the following things:- > 1)CRUD Operation in service & policy module. > 2)service & policy listing pages dropdowns > > > Thanks, > > Brijesh Bhalala > >
Re: Review Request 74489: RANGER-4297: Scroll to Newly added row functionality in listing tables is not working.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74489/#review225565 --- Ship it! Ship It! - Dhaval Rajpara On June 22, 2023, 12:36 p.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74489/ > --- > > (Updated June 22, 2023, 12:36 p.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4297 > https://issues.apache.org/jira/browse/RANGER-4297 > > > Repository: ranger > > > Description > --- > > Steps to reproduce:- > 1)Create a user. > 2)After creating the user it will go to last page of the table. > 3)But it does not scroll to that newly created user > > Current behaviour: > Not get scrolled to newly added row in listing tables > > Expected behaviour: > User should be scroll to newly added row in listing tables > > The last response time is not updated in service manager page when importing > or export the policies. > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/components/CommonComponents.jsx > 7fe756c47 > security-admin/src/main/webapp/react-webapp/src/views/CustomBreadcrumb.jsx > e3ba45f0e > security-admin/src/main/webapp/react-webapp/src/views/Layout.jsx 49edc2861 > > security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListing.jsx > 77797f966 > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ExportPolicy.jsx > d835bfad1 > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ImportPolicy.jsx > 44346bb4b > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx > b77c0fe73 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx > 86059c463 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx > 4e1fc9205 > > > Diff: https://reviews.apache.org/r/74489/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)Verified the following things:- > 1)CRUD Operation in policy & user/group/role module. > 2)policy & user/group/role listing pages. > 3)The last response time is updating when importing or exporting the policies > in service manager page > > > Thanks, > > Brijesh Bhalala > >
Re: Review Request 74488: RANGER-4292: Long zone names are not showing perfectly in the zone search dropdown of service manager
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74488/#review225564 --- Ship it! Ship It! - Dhaval Rajpara On June 22, 2023, 12:26 p.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74488/ > --- > > (Updated June 22, 2023, 12:26 p.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4292 > https://issues.apache.org/jira/browse/RANGER-4292 > > > Repository: ranger > > > Description > --- > > Extra white space gets added at the end of the zone search dropdown when a > long zone name is selected. > > Steps to reproduce: > > 1. create a long zone name like: > >"dffdgfdgfdgdfffdgdfgerfgregregergregregerger" > > 2. Click on the zone search bar on service manager and select the created > zone name. > > 3. Then again click on the search bar and horizontally scroll the search > dropdown. > > 4. There is a long white space added at the end as shown in attached ss. > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx > 05934e447 > security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx > 29b7c1ce9 > > > Diff: https://reviews.apache.org/r/74488/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)Verified the following things:- > 1)CRUD Operation in service & policy module. > 2)service & policy listing pages dropdowns > > > Thanks, > > Brijesh Bhalala > >
Re: Review Request 74487: RANGER-4293: Long User/group/role name overflowing from delete confirmation dialog box
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74487/#review225563 --- Ship it! Ship It! - Dhaval Rajpara On June 22, 2023, 12:15 p.m., Brijesh Bhalala wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74487/ > --- > > (Updated June 22, 2023, 12:15 p.m.) > > > Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan > Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. > > > Bugs: RANGER-4293 > https://issues.apache.org/jira/browse/RANGER-4293 > > > Repository: ranger > > > Description > --- > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > > Steps to reproduce: > > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdg > fdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. > > > Diffs > - > > security-admin/src/main/webapp/react-webapp/src/styles/style.css c8d4dcc4b > security-admin/src/main/webapp/react-webapp/src/views/CustomBreadcrumb.jsx > e3ba45f0e > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx > b77c0fe73 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx > 86059c463 > > security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx > 4e1fc9205 > > > Diff: https://reviews.apache.org/r/74487/diff/1/ > > > Testing > --- > > 1)Build and Verified Ranger Admin setup with this changes. > 2)Verified the following things:- > 1)CRUD Operation in user/group/role module. > 2)user/group/role listing pages. > > > Thanks, > > Brijesh Bhalala > >
[jira] [Updated] (RANGER-4294) Delete message alert box should have message specific to delete activity
[ https://issues.apache.org/jira/browse/RANGER-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4294: --- Attachment: 0001-RABGER-4294.patch > Delete message alert box should have message specific to delete activity > > > Key: RANGER-4294 > URL: https://issues.apache.org/jira/browse/RANGER-4294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RABGER-4294.patch > > > Delete message alert box should have message specific to delete activity. > Try to delete service - Observe - Delete message alert box > Try to delete policy - Observe - Delete message alert box > Both Delete message alert box on same page , no specific details about which > operation is performed > Earlier in backbone Js both deletion happens of different page . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4037) Audits are not getting generated for policy enforcement works based on policy condition
[
https://issues.apache.org/jira/browse/RANGER-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sontakke updated RANGER-4037:
--
Attachment: Ranger - 4037 ticket testing.pdf
> Audits are not getting generated for policy enforcement works based on policy
> condition
>
>
> Key: RANGER-4037
> URL: https://issues.apache.org/jira/browse/RANGER-4037
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Siddhant Sontakke
>Priority: Major
> Attachments: Ranger - 4037 ticket testing.pdf
>
>
> Audits are not getting generated for policy enforcement works based on policy
> condition :
> RangerNoneOfExpectedTagsPresentConditionEvaluator
> Steps to reproduce :
> - Apply policy conditions in service defs
> {code:java}
> "policyConditions": [
> {
> "itemId": 1,
> "name": "all-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerTagsAllPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Tags All Present?",
> "description": "Tags All Present?"
> },
> {
> "itemId": 2,
> "name": "none-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerNoneOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "None of Tags Present?",
> "description": "None of Tags Present?"
> },
> {
> "itemId": 3,
> "name": "any-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerAnyOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Any of Tags Present?",
> "description": "Any of Tags Present?"
> } ], {code}
> Add tag based policy for with
> RangerNoneOfExpectedTagsPresentConditionEvaluator tag including tag which is
> used to created policy and give hive access to user
> Try access tag related attribute in beeline
> User will be denied and policy is enforced but in audit logs denied policy
> wont be available .
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4037) Audits are not getting generated for policy enforcement works based on policy condition
[
https://issues.apache.org/jira/browse/RANGER-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sontakke updated RANGER-4037:
--
Attachment: Ranger - 4037 ticket testing.pdf
> Audits are not getting generated for policy enforcement works based on policy
> condition
>
>
> Key: RANGER-4037
> URL: https://issues.apache.org/jira/browse/RANGER-4037
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Siddhant Sontakke
>Priority: Major
> Attachments: Ranger - 4037 ticket testing.pdf
>
>
> Audits are not getting generated for policy enforcement works based on policy
> condition :
> RangerNoneOfExpectedTagsPresentConditionEvaluator
> Steps to reproduce :
> - Apply policy conditions in service defs
> {code:java}
> "policyConditions": [
> {
> "itemId": 1,
> "name": "all-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerTagsAllPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Tags All Present?",
> "description": "Tags All Present?"
> },
> {
> "itemId": 2,
> "name": "none-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerNoneOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "None of Tags Present?",
> "description": "None of Tags Present?"
> },
> {
> "itemId": 3,
> "name": "any-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerAnyOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Any of Tags Present?",
> "description": "Any of Tags Present?"
> } ], {code}
> Add tag based policy for with
> RangerNoneOfExpectedTagsPresentConditionEvaluator tag including tag which is
> used to created policy and give hive access to user
> Try access tag related attribute in beeline
> User will be denied and policy is enforced but in audit logs denied policy
> wont be available .
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4037) Audits are not getting generated for policy enforcement works based on policy condition
[
https://issues.apache.org/jira/browse/RANGER-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sontakke updated RANGER-4037:
--
Attachment: (was: Ranger - 4037 ticket testing.pdf)
> Audits are not getting generated for policy enforcement works based on policy
> condition
>
>
> Key: RANGER-4037
> URL: https://issues.apache.org/jira/browse/RANGER-4037
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Siddhant Sontakke
>Priority: Major
> Attachments: Ranger - 4037 ticket testing.pdf
>
>
> Audits are not getting generated for policy enforcement works based on policy
> condition :
> RangerNoneOfExpectedTagsPresentConditionEvaluator
> Steps to reproduce :
> - Apply policy conditions in service defs
> {code:java}
> "policyConditions": [
> {
> "itemId": 1,
> "name": "all-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerTagsAllPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Tags All Present?",
> "description": "Tags All Present?"
> },
> {
> "itemId": 2,
> "name": "none-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerNoneOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "None of Tags Present?",
> "description": "None of Tags Present?"
> },
> {
> "itemId": 3,
> "name": "any-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerAnyOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Any of Tags Present?",
> "description": "Any of Tags Present?"
> } ], {code}
> Add tag based policy for with
> RangerNoneOfExpectedTagsPresentConditionEvaluator tag including tag which is
> used to created policy and give hive access to user
> Try access tag related attribute in beeline
> User will be denied and policy is enforced but in audit logs denied policy
> wont be available .
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4037) Audits are not getting generated for policy enforcement works based on policy condition
[
https://issues.apache.org/jira/browse/RANGER-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736125#comment-17736125
]
Siddhant Sontakke commented on RANGER-4037:
---
[~anupamrai2303] could you please take a look? I have tested the ticket, and
everything is working fine in my case. I am sharing a document in which I have
mentioned all the steps to reproduce the issue. Could you review it?
[^Ranger - 4037 ticket testing.pdf]
> Audits are not getting generated for policy enforcement works based on policy
> condition
>
>
> Key: RANGER-4037
> URL: https://issues.apache.org/jira/browse/RANGER-4037
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Siddhant Sontakke
>Priority: Major
> Attachments: Ranger - 4037 ticket testing.pdf
>
>
> Audits are not getting generated for policy enforcement works based on policy
> condition :
> RangerNoneOfExpectedTagsPresentConditionEvaluator
> Steps to reproduce :
> - Apply policy conditions in service defs
> {code:java}
> "policyConditions": [
> {
> "itemId": 1,
> "name": "all-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerTagsAllPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Tags All Present?",
> "description": "Tags All Present?"
> },
> {
> "itemId": 2,
> "name": "none-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerNoneOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "None of Tags Present?",
> "description": "None of Tags Present?"
> },
> {
> "itemId": 3,
> "name": "any-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerAnyOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Any of Tags Present?",
> "description": "Any of Tags Present?"
> } ], {code}
> Add tag based policy for with
> RangerNoneOfExpectedTagsPresentConditionEvaluator tag including tag which is
> used to created policy and give hive access to user
> Try access tag related attribute in beeline
> User will be denied and policy is enforced but in audit logs denied policy
> wont be available .
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4297) [Ranger UI] [React JS] Scroll to Newly added row functionality in listing tables is not working.
[ https://issues.apache.org/jira/browse/RANGER-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4297: Labels: ranger-react (was: ) > [Ranger UI] [React JS] Scroll to Newly added row functionality in listing > tables is not working. > > > Key: RANGER-4297 > URL: https://issues.apache.org/jira/browse/RANGER-4297 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4297.patch > > > Steps to reproduce:- > 1)Create a user. > 2)After creating the user it will go to last page of the table. > 3)But it does not scroll to that newly created user > Current behaviour: > Not get scrolled to newly added row in listing tables > > Expected behaviour: > User should be scroll to newly added row in listing tables > * The last response time is not updated in service manager page when > importing or export the policies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4296) [Ranger UI] [React JS] Dropdown option in the access audits must display "User" instead of "Users"
[
https://issues.apache.org/jira/browse/RANGER-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek updated RANGER-4296:
-
Fix Version/s: 3.0.0
> [Ranger UI] [React JS] Dropdown option in the access audits must display
> "User" instead of "Users"
> --
>
> Key: RANGER-4296
> URL: https://issues.apache.org/jira/browse/RANGER-4296
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Labels: ranger-react
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-4296-Ranger-UI-React-JS-Dropdown-option-in-th.patch
>
>
> {color:#172b4d}In the options to filter the access audits in the react JS UI,
> the option to filter by username must be displayed as "User" instead of
> "Users".{color}
> {color:#172b4d}Even in the old UI's, the option is displayed as "User"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74489: RANGER-4297: Scroll to Newly added row functionality in listing tables is not working.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74489/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4297 https://issues.apache.org/jira/browse/RANGER-4297 Repository: ranger Description --- Steps to reproduce:- 1)Create a user. 2)After creating the user it will go to last page of the table. 3)But it does not scroll to that newly created user Current behaviour: Not get scrolled to newly added row in listing tables Expected behaviour: User should be scroll to newly added row in listing tables The last response time is not updated in service manager page when importing or export the policies. Diffs - security-admin/src/main/webapp/react-webapp/src/components/CommonComponents.jsx 7fe756c47 security-admin/src/main/webapp/react-webapp/src/views/CustomBreadcrumb.jsx e3ba45f0e security-admin/src/main/webapp/react-webapp/src/views/Layout.jsx 49edc2861 security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListing.jsx 77797f966 security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ExportPolicy.jsx d835bfad1 security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ImportPolicy.jsx 44346bb4b security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx b77c0fe73 security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx 86059c463 security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx 4e1fc9205 Diff: https://reviews.apache.org/r/74489/diff/1/ Testing --- 1)Build and Verified Ranger Admin setup with this changes. 2)Verified the following things:- 1)CRUD Operation in policy & user/group/role module. 2)policy & user/group/role listing pages. 3)The last response time is updating when importing or exporting the policies in service manager page Thanks, Brijesh Bhalala
[jira] [Updated] (RANGER-4297) [Ranger UI] [React JS] Scroll to Newly added row functionality in listing tables is not working.
[ https://issues.apache.org/jira/browse/RANGER-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4297: Description: Steps to reproduce:- 1)Create a user. 2)After creating the user it will go to last page of the table. 3)But it does not scroll to that newly created user Current behaviour: Not get scrolled to newly added row in listing tables Expected behaviour: User should be scroll to newly added row in listing tables * The last response time is not updated in service manager page when importing or export the policies. was: Steps to reproduce:- 1)Create a user. 2)After creating the user it will go to last page of the table. 3)But it does not scroll to that newly created user Current behaviour: Not get scrolled to newly added row in listing tables Expected behaviour: User should be scroll to newly added row in listing tables > [Ranger UI] [React JS] Scroll to Newly added row functionality in listing > tables is not working. > > > Key: RANGER-4297 > URL: https://issues.apache.org/jira/browse/RANGER-4297 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4297.patch > > > Steps to reproduce:- > 1)Create a user. > 2)After creating the user it will go to last page of the table. > 3)But it does not scroll to that newly created user > Current behaviour: > Not get scrolled to newly added row in listing tables > > Expected behaviour: > User should be scroll to newly added row in listing tables > * The last response time is not updated in service manager page when > importing or export the policies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4297) [Ranger UI] [React JS] Scroll to Newly added row functionality in listing tables is not working.
[ https://issues.apache.org/jira/browse/RANGER-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4297: Attachment: 0001-RANGER-4297.patch > [Ranger UI] [React JS] Scroll to Newly added row functionality in listing > tables is not working. > > > Key: RANGER-4297 > URL: https://issues.apache.org/jira/browse/RANGER-4297 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4297.patch > > > Steps to reproduce:- > 1)Create a user. > 2)After creating the user it will go to last page of the table. > 3)But it does not scroll to that newly created user > Current behaviour: > Not get scrolled to newly added row in listing tables > > Expected behaviour: > User should be scroll to newly added row in listing tables -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4292) [Ranger UI] [React JS] Long zone names are not showing perfectly in the zone search dropdown of service manager
[ https://issues.apache.org/jira/browse/RANGER-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4292: Fix Version/s: 3.0.0 > [Ranger UI] [React JS] Long zone names are not showing perfectly in the zone > search dropdown of service manager > --- > > Key: RANGER-4292 > URL: https://issues.apache.org/jira/browse/RANGER-4292 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4292.patch, Screenshot 2023-06-19 at 4.40.35 > PM.png > > > Extra white space gets added at the end of the zone search dropdown when a > long zone name is selected. > > Steps to reproduce: > 1. create a long zone name like: > "dffdgfdgfdgdfffdgdfgerfgregregergregregerger" > 2. Click on the zone search bar on service manager and select the created > zone name. > 3. Then again click on the search bar and horizontally scroll the search > dropdown. > 4. There is a long white space added at the end as shown in attached ss. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4292) [Ranger UI] [React JS] Long zone names are not showing perfectly in the zone search dropdown of service manager
[ https://issues.apache.org/jira/browse/RANGER-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4292: Attachment: 0001-RANGER-4292.patch > [Ranger UI] [React JS] Long zone names are not showing perfectly in the zone > search dropdown of service manager > --- > > Key: RANGER-4292 > URL: https://issues.apache.org/jira/browse/RANGER-4292 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4292.patch, Screenshot 2023-06-19 at 4.40.35 > PM.png > > > Extra white space gets added at the end of the zone search dropdown when a > long zone name is selected. > > Steps to reproduce: > 1. create a long zone name like: > "dffdgfdgfdgdfffdgdfgerfgregregergregregerger" > 2. Click on the zone search bar on service manager and select the created > zone name. > 3. Then again click on the search bar and horizontally scroll the search > dropdown. > 4. There is a long white space added at the end as shown in attached ss. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74488: RANGER-4292: Long zone names are not showing perfectly in the zone search dropdown of service manager
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74488/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4292 https://issues.apache.org/jira/browse/RANGER-4292 Repository: ranger Description --- Extra white space gets added at the end of the zone search dropdown when a long zone name is selected. Steps to reproduce: 1. create a long zone name like: "dffdgfdgfdgdfffdgdfgerfgregregergregregerger" 2. Click on the zone search bar on service manager and select the created zone name. 3. Then again click on the search bar and horizontally scroll the search dropdown. 4. There is a long white space added at the end as shown in attached ss. Diffs - security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx 05934e447 security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx 29b7c1ce9 Diff: https://reviews.apache.org/r/74488/diff/1/ Testing --- 1)Build and Verified Ranger Admin setup with this changes. 2)Verified the following things:- 1)CRUD Operation in service & policy module. 2)service & policy listing pages dropdowns Thanks, Brijesh Bhalala
[jira] [Updated] (RANGER-4293) [Ranger UI] [React JS] Long User/group/role name overflowing from delete confirmation dialog box
[ https://issues.apache.org/jira/browse/RANGER-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4293: Fix Version/s: 3.0.0 > [Ranger UI] [React JS] Long User/group/role name overflowing from delete > confirmation dialog box > > > Key: RANGER-4293 > URL: https://issues.apache.org/jira/browse/RANGER-4293 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4293.patch, Screenshot 2023-06-19 at 3.05.26 > PM.png > > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > Steps to reproduce: > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdgfdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4293) [Ranger UI] [React JS] Long User/group/role name overflowing from delete confirmation dialog box
[ https://issues.apache.org/jira/browse/RANGER-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4293: Attachment: 0001-RANGER-4293.patch > [Ranger UI] [React JS] Long User/group/role name overflowing from delete > confirmation dialog box > > > Key: RANGER-4293 > URL: https://issues.apache.org/jira/browse/RANGER-4293 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4293.patch, Screenshot 2023-06-19 at 3.05.26 > PM.png > > > When tried to delete a single user/group/role from UI. Inside the delete > confirmation prompt the name of the entity is overflowing if the name is very > large. > Steps to reproduce: > 1. create a user with very large username like > "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdgfdgfdgfd" > 2. Then try to delete it from the UI. > 3. The name of the user flow out of the confirmation prompt. > > Current behaviour: > The username is flowing out of the confirmation prompt. > > Expected behaviour: > The username should be inside the confirmation prompt. If required there may > be a scroll. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74487: RANGER-4293: Long User/group/role name overflowing from delete confirmation dialog box
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74487/ --- Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave. Bugs: RANGER-4293 https://issues.apache.org/jira/browse/RANGER-4293 Repository: ranger Description --- When tried to delete a single user/group/role from UI. Inside the delete confirmation prompt the name of the entity is overflowing if the name is very large. Steps to reproduce: 1. create a user with very large username like "some_uresrnasjdsadjsadjksadjasdakdsakdsayrfytrtydtrdrtsrtdtrdtrdtrdrtdrtdtrdtrdrtdfggt4gfefgfdvfdgfdgfdg fdgfdgfd" 2. Then try to delete it from the UI. 3. The name of the user flow out of the confirmation prompt. Current behaviour: The username is flowing out of the confirmation prompt. Expected behaviour: The username should be inside the confirmation prompt. If required there may be a scroll. Diffs - security-admin/src/main/webapp/react-webapp/src/styles/style.css c8d4dcc4b security-admin/src/main/webapp/react-webapp/src/views/CustomBreadcrumb.jsx e3ba45f0e security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/groups_details/GroupListing.jsx b77c0fe73 security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/role_details/RoleListing.jsx 86059c463 security-admin/src/main/webapp/react-webapp/src/views/UserGroupRoleListing/users_details/UserListing.jsx 4e1fc9205 Diff: https://reviews.apache.org/r/74487/diff/1/ Testing --- 1)Build and Verified Ranger Admin setup with this changes. 2)Verified the following things:- 1)CRUD Operation in user/group/role module. 2)user/group/role listing pages. Thanks, Brijesh Bhalala
[jira] [Commented] (RANGER-4296) [Ranger UI] [React JS] Dropdown option in the access audits must display "User" instead of "Users"
[
https://issues.apache.org/jira/browse/RANGER-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736093#comment-17736093
]
Dineshkumar Yadav commented on RANGER-4296:
---
commit :
https://github.com/apache/ranger/commit/fe7f7b04e22805ab4367c8043e01cf8b0e358ce4
> [Ranger UI] [React JS] Dropdown option in the access audits must display
> "User" instead of "Users"
> --
>
> Key: RANGER-4296
> URL: https://issues.apache.org/jira/browse/RANGER-4296
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Attachments:
> 0001-RANGER-4296-Ranger-UI-React-JS-Dropdown-option-in-th.patch
>
>
> {color:#172b4d}In the options to filter the access audits in the react JS UI,
> the option to filter by username must be displayed as "User" instead of
> "Users".{color}
> {color:#172b4d}Even in the old UI's, the option is displayed as "User"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4296) [Ranger UI] [React JS] Dropdown option in the access audits must display "User" instead of "Users"
[
https://issues.apache.org/jira/browse/RANGER-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek updated RANGER-4296:
-
Labels: ranger-react (was: )
> [Ranger UI] [React JS] Dropdown option in the access audits must display
> "User" instead of "Users"
> --
>
> Key: RANGER-4296
> URL: https://issues.apache.org/jira/browse/RANGER-4296
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Labels: ranger-react
> Attachments:
> 0001-RANGER-4296-Ranger-UI-React-JS-Dropdown-option-in-th.patch
>
>
> {color:#172b4d}In the options to filter the access audits in the react JS UI,
> the option to filter by username must be displayed as "User" instead of
> "Users".{color}
> {color:#172b4d}Even in the old UI's, the option is displayed as "User"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-4296) [Ranger UI] [React JS] Dropdown option in the access audits must display "User" instead of "Users"
[
https://issues.apache.org/jira/browse/RANGER-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek resolved RANGER-4296.
--
Resolution: Fixed
> [Ranger UI] [React JS] Dropdown option in the access audits must display
> "User" instead of "Users"
> --
>
> Key: RANGER-4296
> URL: https://issues.apache.org/jira/browse/RANGER-4296
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Attachments:
> 0001-RANGER-4296-Ranger-UI-React-JS-Dropdown-option-in-th.patch
>
>
> {color:#172b4d}In the options to filter the access audits in the react JS UI,
> the option to filter by username must be displayed as "User" instead of
> "Users".{color}
> {color:#172b4d}Even in the old UI's, the option is displayed as "User"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74486: RANGER-4296: [Ranger UI] [React JS] Dropdown option in the access audits must display "User" instead of "Users"
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74486/#review225562 --- Ship it! Ship It! - Dhaval Rajpara On June 22, 2023, 6:06 a.m., Abhishek Patil wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74486/ > --- > > (Updated June 22, 2023, 6:06 a.m.) > > > Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, Mehul Parikh, and > Mugdha Varadkar. > > > Bugs: RANGER-4296 > https://issues.apache.org/jira/browse/RANGER-4296 > > > Repository: ranger > > > Description > --- > > In the options to filter the access audits in the react JS UI, the option to > filter by username must be displayed as "User" instead of "Users". > Even in the old UI's, the option is displayed as "User" > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AccessLogs.jsx > bd8011fd5 > > > Diff: https://reviews.apache.org/r/74486/diff/1/ > > > Testing > --- > > Tested locally > > > Thanks, > > Abhishek Patil > >
[jira] [Assigned] (RANGER-4037) Audits are not getting generated for policy enforcement works based on policy condition
[
https://issues.apache.org/jira/browse/RANGER-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sontakke reassigned RANGER-4037:
-
Assignee: Siddhant Sontakke
> Audits are not getting generated for policy enforcement works based on policy
> condition
>
>
> Key: RANGER-4037
> URL: https://issues.apache.org/jira/browse/RANGER-4037
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Assignee: Siddhant Sontakke
>Priority: Major
>
> Audits are not getting generated for policy enforcement works based on policy
> condition :
> RangerNoneOfExpectedTagsPresentConditionEvaluator
> Steps to reproduce :
> - Apply policy conditions in service defs
> {code:java}
> "policyConditions": [
> {
> "itemId": 1,
> "name": "all-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerTagsAllPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Tags All Present?",
> "description": "Tags All Present?"
> },
> {
> "itemId": 2,
> "name": "none-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerNoneOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "None of Tags Present?",
> "description": "None of Tags Present?"
> },
> {
> "itemId": 3,
> "name": "any-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerAnyOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Any of Tags Present?",
> "description": "Any of Tags Present?"
> } ], {code}
> Add tag based policy for with
> RangerNoneOfExpectedTagsPresentConditionEvaluator tag including tag which is
> used to created policy and give hive access to user
> Try access tag related attribute in beeline
> User will be denied and policy is enforced but in audit logs denied policy
> wont be available .
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4037) Audits are not getting generated for policy enforcement works based on policy condition
[
https://issues.apache.org/jira/browse/RANGER-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sneha_surjuse reassigned RANGER-4037:
-
Assignee: (was: sneha_surjuse)
> Audits are not getting generated for policy enforcement works based on policy
> condition
>
>
> Key: RANGER-4037
> URL: https://issues.apache.org/jira/browse/RANGER-4037
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Anupam Rai
>Priority: Major
>
> Audits are not getting generated for policy enforcement works based on policy
> condition :
> RangerNoneOfExpectedTagsPresentConditionEvaluator
> Steps to reproduce :
> - Apply policy conditions in service defs
> {code:java}
> "policyConditions": [
> {
> "itemId": 1,
> "name": "all-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerTagsAllPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Tags All Present?",
> "description": "Tags All Present?"
> },
> {
> "itemId": 2,
> "name": "none-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerNoneOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "None of Tags Present?",
> "description": "None of Tags Present?"
> },
> {
> "itemId": 3,
> "name": "any-of-tag-present",
> "evaluator":
> "org.apache.ranger.plugin.conditionevaluator.RangerAnyOfExpectedTagsPresentConditionEvaluator",
> "evaluatorOptions": {},
> "label": "Any of Tags Present?",
> "description": "Any of Tags Present?"
> } ], {code}
> Add tag based policy for with
> RangerNoneOfExpectedTagsPresentConditionEvaluator tag including tag which is
> used to created policy and give hive access to user
> Try access tag related attribute in beeline
> User will be denied and policy is enforced but in audit logs denied policy
> wont be available .
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
