Re: Review Request 74538: RANGER-4345 plugin side metrics on polling from the policy server

[Ramesh Mani]

> On Aug. 8, 2023, 10:45 p.m., Ramesh Mani wrote:
> > agents-common/src/main/java/org/apache/ranger/plugin/util/PolicyRefresher.java
> > Lines 121 (patched)
> > 
> >
> > Thanks for the contribution.
> > Could you please have the MetricRegistry() as a generic 
> > RangerMetricRegistry() in org.apache.ranger.plugin.util package of 
> > agents-common module and have the other services like PolicyRefresh which 
> > you have implemented on can utilize it?
> 
> Sai Sandeep Rangisetti wrote:
> Should I make it static/singleton class or should it be so that all the 
> classes like PolicyRefresher or RangerRESTClient make thier own instance of 
> RangerMetricRegistry. Is there a better way I can depend on 
> RangerMetricRegistry.

Please make it as regular class so other services can instantiate it. Since 
plugins are the one which is going to use it lets have it agents-common only.


- Ramesh


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


On Aug. 8, 2023, 3:32 p.m., Sai Sandeep Rangisetti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74538/
> ---
> 
> (Updated Aug. 8, 2023, 3:32 p.m.)
> 
> 
> Review request for ranger, Kishor Gollapalliwar, Abhay Kulkarni, Madhan 
> Neethiraj, Mehul Parikh, Pradeep Agrawal, and Ramachandran Krishnan.
> 
> 
> Bugs: RANGER-4345
> https://issues.apache.org/jira/browse/RANGER-4345
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add metrics in the plugins for increased visibility on what is happening in 
> the systems
> 
> 
> Diffs
> -
> 
>   agents-common/pom.xml b753c1368 
>   
> agents-common/src/main/java/org/apache/ranger/authorization/hadoop/config/RangerConfigConstants.java
>  374c78c5e 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/PolicyRefresher.java
>  c130309ea 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTClient.java
>  e54313403 
> 
> 
> Diff: https://reviews.apache.org/r/74538/diff/2/
> 
> 
> Testing
> ---
> 
> Compiled and installed the hbase plugin and verified that metrics are being 
> published to jmx. Simulated failures by blocking port and verified timeout 
> and retry metrics are also being published
> 
> 
> Thanks,
> 
> Sai Sandeep Rangisetti
> 
>

Review Request 74542: RANGER-4346: Need to Change type of column resource_signature in table x_gds_shared_resource to TEXT

[Prashant Satam]

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

Review request for ranger, Madhan Neethiraj and Subhrat Chaudhary.


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


Repository: ranger


Description
---

Need to change the type of column resource_signature in table 
x_gds_shared_resource to text from present varchar(128) ,As customers will have 
large data so existing size will not be enough


Diffs
-

  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql b4e3f57b8 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
6b82aead4 


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


Testing
---

When we create tables by schema we can see the TYPE for column 
resource_signature as TEXT which was previously varchar(128)


Thanks,

Prashant Satam

[jira] [Commented] (RANGER-4349) AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES

[Ramesh Mani (Jira)]

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

Ramesh Mani commented on RANGER-4349:
-

[~szyorz]  Thank you for the contribution. Committed to apache ranger master 
https://github.com/apache/ranger/commit/a5461808742ef0f40410f326fdf236619e81ca4f

> AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES
> --
>
> Key: RANGER-4349
> URL: https://issues.apache.org/jira/browse/RANGER-4349
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Szymon Orzechowski
>Assignee: Szymon Orzechowski
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4349.patch
>
>
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
> ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
> received by Ranger Tagsync is determined by 
> atlas.notification.entities.topic.name property in 
> atlas-application.properties file. By default, it is ATLAS_ENTITIES but some 
> might configure it to a different name in which case Tagsync would be 
> committing offset to the wrong topic.
>  



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

[jira] [Updated] (RANGER-4349) AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES

[Ramesh Mani (Jira)]

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

Ramesh Mani updated RANGER-4349:

Fix Version/s: 3.0.0

> AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES
> --
>
> Key: RANGER-4349
> URL: https://issues.apache.org/jira/browse/RANGER-4349
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Szymon Orzechowski
>Assignee: Szymon Orzechowski
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4349.patch
>
>
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
> ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
> received by Ranger Tagsync is determined by 
> atlas.notification.entities.topic.name property in 
> atlas-application.properties file. By default, it is ATLAS_ENTITIES but some 
> might configure it to a different name in which case Tagsync would be 
> committing offset to the wrong topic.
>  



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

Re: Review Request 74541: RANGER-4349: AtlasTagSource.commitToKafka() should commit the offset to the topic from which the message came from.

[Ramesh Mani]

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


Ship it!




Ship It!

- Ramesh Mani


On Aug. 9, 2023, 8:03 p.m., Szymon Orzechowski wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74541/
> ---
> 
> (Updated Aug. 9, 2023, 8:03 p.m.)
> 
> 
> Review request for ranger, Abhishek  Kumar and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-4349
> https://issues.apache.org/jira/browse/RANGER-4349
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
> ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
> received by Ranger Tagsync is determined by 
> atlas.notification.entities.topic.name property in 
> atlas-application.properties file. By default, it is ATLAS_ENTITIES but some 
> might configure it to a different name in which case Tagsync would be 
> committing offset to the wrong topic.
> 
> 
> Diffs
> -
> 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java
>  071f52c4a 
> 
> 
> Diff: https://reviews.apache.org/r/74541/diff/1/
> 
> 
> Testing
> ---
> 
> Checked on my cluster and verified if `mvn clean test` passes
> 
> 
> Thanks,
> 
> Szymon Orzechowski
> 
>

Re: Review Request 74541: RANGER-4349: AtlasTagSource.commitToKafka() should commit the offset to the topic from which the message came from.

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On Aug. 9, 2023, 8:03 p.m., Szymon Orzechowski wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74541/
> ---
> 
> (Updated Aug. 9, 2023, 8:03 p.m.)
> 
> 
> Review request for ranger, Abhishek  Kumar and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-4349
> https://issues.apache.org/jira/browse/RANGER-4349
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
> ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
> received by Ranger Tagsync is determined by 
> atlas.notification.entities.topic.name property in 
> atlas-application.properties file. By default, it is ATLAS_ENTITIES but some 
> might configure it to a different name in which case Tagsync would be 
> committing offset to the wrong topic.
> 
> 
> Diffs
> -
> 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java
>  071f52c4a 
> 
> 
> Diff: https://reviews.apache.org/r/74541/diff/1/
> 
> 
> Testing
> ---
> 
> Checked on my cluster and verified if `mvn clean test` passes
> 
> 
> Thanks,
> 
> Szymon Orzechowski
> 
>

[jira] [Commented] (RANGER-4349) AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES

[Szymon Orzechowski (Jira)]

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

Szymon Orzechowski commented on RANGER-4349:


Review board: https://reviews.apache.org/r/74541/

> AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES
> --
>
> Key: RANGER-4349
> URL: https://issues.apache.org/jira/browse/RANGER-4349
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Szymon Orzechowski
>Assignee: Szymon Orzechowski
>Priority: Major
> Attachments: RANGER-4349.patch
>
>
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
> ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
> received by Ranger Tagsync is determined by 
> atlas.notification.entities.topic.name property in 
> atlas-application.properties file. By default, it is ATLAS_ENTITIES but some 
> might configure it to a different name in which case Tagsync would be 
> committing offset to the wrong topic.
>  



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

Review Request 74541: RANGER-4349: AtlasTagSource.commitToKafka() should commit the offset to the topic from which the message came from.

[Szymon Orzechowski via Review Board]

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

Review request for ranger, Abhishek  Kumar and Madhan Neethiraj.


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


Repository: ranger


Description
---

AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
received by Ranger Tagsync is determined by 
atlas.notification.entities.topic.name property in atlas-application.properties 
file. By default, it is ATLAS_ENTITIES but some might configure it to a 
different name in which case Tagsync would be committing offset to the wrong 
topic.


Diffs
-

  
tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java
 071f52c4a 


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


Testing
---

Checked on my cluster and verified if `mvn clean test` passes


Thanks,

Szymon Orzechowski

[jira] [Updated] (RANGER-4349) AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES

[Szymon Orzechowski (Jira)]

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

Szymon Orzechowski updated RANGER-4349:
---
Attachment: RANGER-4349.patch

> AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES
> --
>
> Key: RANGER-4349
> URL: https://issues.apache.org/jira/browse/RANGER-4349
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Szymon Orzechowski
>Assignee: Szymon Orzechowski
>Priority: Major
> Attachments: RANGER-4349.patch
>
>
> AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
> ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
> received by Ranger Tagsync is determined by 
> atlas.notification.entities.topic.name property in 
> atlas-application.properties file. By default, it is ATLAS_ENTITIES but some 
> might configure it to a different name in which case Tagsync would be 
> committing offset to the wrong topic.
>  



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

[jira] [Created] (RANGER-4349) AtlasTagSource is hardcoded to commit offset to ATLAS_ENTITIES

[Szymon Orzechowski (Jira)]

Szymon Orzechowski created RANGER-4349:
--

 Summary: AtlasTagSource is hardcoded to commit offset to 
ATLAS_ENTITIES
 Key: RANGER-4349
 URL: https://issues.apache.org/jira/browse/RANGER-4349
 Project: Ranger
  Issue Type: Bug
  Components: tagsync
Affects Versions: 2.4.0, 3.0.0
Reporter: Szymon Orzechowski
Assignee: Szymon Orzechowski


AtlasTagSource.commitToKafka() is hard coded to commit offset to topic 
ATLAS_ENTITIES.  The topic to which entity events are sent from Atlas and 
received by Ranger Tagsync is determined by 
atlas.notification.entities.topic.name property in atlas-application.properties 
file. By default, it is ATLAS_ENTITIES but some might configure it to a 
different name in which case Tagsync would be committing offset to the wrong 
topic.

 



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

[GitHub] [ranger] sercanCyberVision commented on pull request #252: RANGER-4225: Possible Jackson serialization issue due to not comply with Java bean standards

[via GitHub]

sercanCyberVision commented on PR #252:
URL: https://github.com/apache/ranger/pull/252#issuecomment-1671905549

   @mneethiraj could you please take a look at this? I hit this issue earlier, 
and the solution here can save some grief for the end-users for the future.


-- 
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 74522: RANGER-4328: updated resource matcher handling of SELF_OR_PREFIX scope

[Madhan Neethiraj]

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




agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java
Line 39 (original), 41 (patched)


> the scope is set to SELF
matchType here is not an input to the matcher; it is the expected value 
from ResourceMatcher implementation.

A policy having "*" will match every resource; the same policy with 
excludes=true will match no resource. Hence the expected matchType=NONE and 
result=false.



agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java
Line 42 (original), 44 (patched)


> Here, the matchType is NONE, and when compared with NONE
Same as the response to the previous comment. matchType here is not an 
input to ResourceMatcher implementation. It is the expected output.


- Madhan Neethiraj


On July 25, 2023, 8:34 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74522/
> ---
> 
> (Updated July 25, 2023, 8:34 p.m.)
> 
> 
> Review request for ranger, Hayat Behlim, Abhay Kulkarni, Mehul Parikh, Monika 
> Kachhadiya, Ramesh Mani, Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4328
> https://issues.apache.org/jira/browse/RANGER-4328
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> updated ResourceMatcher.isPrefixMatch() implementations to handle wildcards 
> correctly
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerAbstractResourceMatcher.java
>  cb8d46adf 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcher.java
>  702cb272f 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerPathResourceMatcher.java
>  3c1523c25 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerResourceMatcher.java
>  c4ce30d36 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerURLResourceMatcher.java
>  ce73b3006 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/ResourceMatcher.java
>  ad0942fbe 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerAbstractResourceMatcherTest.java
>  767795e81 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java
>  e00bc834d 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerPathResourceMatcherTest.java
>  ed02be674 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerURLResourceMatcherTest.java
>  904cb61b2 
> 
> 
> Diff: https://reviews.apache.org/r/74522/diff/4/
> 
> 
> Testing
> ---
> 
> - updated unittests to include wildcards at the beginning and in the middle 
> of policy values
> - verified that all unit tests pass successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Review Request 74522: RANGER-4328: updated resource matcher handling of SELF_OR_PREFIX scope

[Abhay Kulkarni]

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




agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java
Line 39 (original), 41 (patched)


Why is the expected result 'false'? As I understand, the scope is set to 
SELF, and therefore it should return match-type as SELF. Comparing SELF with 
NONE should return 'false' which is reversed as the excludes flag is set to 
true. Therefore, the final expected result should be 'true'.



agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java
Line 42 (original), 44 (patched)


Here, the matchType is NONE, and when compared with NONE, should return 
true. So, the expected result should be 'true'.


- Abhay Kulkarni


On July 25, 2023, 8:34 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74522/
> ---
> 
> (Updated July 25, 2023, 8:34 p.m.)
> 
> 
> Review request for ranger, Hayat Behlim, Abhay Kulkarni, Mehul Parikh, Monika 
> Kachhadiya, Ramesh Mani, Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4328
> https://issues.apache.org/jira/browse/RANGER-4328
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> updated ResourceMatcher.isPrefixMatch() implementations to handle wildcards 
> correctly
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerAbstractResourceMatcher.java
>  cb8d46adf 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcher.java
>  702cb272f 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerPathResourceMatcher.java
>  3c1523c25 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerResourceMatcher.java
>  c4ce30d36 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/RangerURLResourceMatcher.java
>  ce73b3006 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/resourcematcher/ResourceMatcher.java
>  ad0942fbe 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerAbstractResourceMatcherTest.java
>  767795e81 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java
>  e00bc834d 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerPathResourceMatcherTest.java
>  ed02be674 
>   
> agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerURLResourceMatcherTest.java
>  904cb61b2 
> 
> 
> Diff: https://reviews.apache.org/r/74522/diff/4/
> 
> 
> Testing
> ---
> 
> - updated unittests to include wildcards at the beginning and in the middle 
> of policy values
> - verified that all unit tests pass successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

[jira] [Updated] (RANGER-4347) User name with comma spited in old Ranger admin UI .

[Dhaval Rajpara (Jira)]

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

Dhaval Rajpara updated RANGER-4347:
---
Summary: User name with comma spited in old Ranger admin UI .  (was: User 
name with "," spited in old Ranger admin UI .)

> User name with comma spited in old Ranger admin UI .
> 
>
> Key: RANGER-4347
> URL: https://issues.apache.org/jira/browse/RANGER-4347
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
>
> when using Ranger Audit filter to filter out the audit for a specific user:
> Usually, if we input a username, it would be no issue, but if we input the 
> user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”.
> We found that once we saved the audit filter policy, the user was split into 
> “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com”
> It happens because Ranger UI recognize “,” to be separate items.
> Same scenario is present in :
> 1) Security Zone Form 
> 2) Permission modules
> 3) Role Form



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

[jira] [Assigned] (RANGER-4348) Filter audits for cc_metric_reporter user on Kafka service repo

[Abhishek (Jira)]

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

Abhishek reassigned RANGER-4348:


Assignee: Abhishek

> Filter audits for cc_metric_reporter user on Kafka service repo
> ---
>
> Key: RANGER-4348
> URL: https://issues.apache.org/jira/browse/RANGER-4348
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> A lot of audits are generated for cc_metric_reporter user for the kafka 
> service repo for the resource "__CruiseControlMetrics".
> These audits will fill up the audit logs, and not much value is added by 
> these audits.
> Hence, it will be better to add a default audit filter to filter the audits 
> from cc_metric_reporter user on the kafka service repo.



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

[jira] [Created] (RANGER-4348) Filter audits for cc_metric_reporter user on Kafka service repo

[Abhishek (Jira)]

Abhishek created RANGER-4348:


 Summary: Filter audits for cc_metric_reporter user on Kafka 
service repo
 Key: RANGER-4348
 URL: https://issues.apache.org/jira/browse/RANGER-4348
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Reporter: Abhishek


A lot of audits are generated for cc_metric_reporter user for the kafka service 
repo for the resource "__CruiseControlMetrics".
These audits will fill up the audit logs, and not much value is added by these 
audits.
Hence, it will be better to add a default audit filter to filter the audits 
from cc_metric_reporter user on the kafka service repo.



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

[jira] [Updated] (RANGER-4346) Need to Change type of column resource_signature in table x_gds_shared_resource to TEXT

[Prashant Satam (Jira)]

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

Prashant Satam updated RANGER-4346:
---
Description: Need to change the type of column resource_signature in table 
x_gds_shared_resource to text from present varchar(128) ,As customers will have 
large data so existing size will not be enough   (was: Need to change the type 
of )

> Need to Change type of column resource_signature in table 
> x_gds_shared_resource to TEXT
> ---
>
> Key: RANGER-4346
> URL: https://issues.apache.org/jira/browse/RANGER-4346
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Minor
>
> Need to change the type of column resource_signature in table 
> x_gds_shared_resource to text from present varchar(128) ,As customers will 
> have large data so existing size will not be enough 



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

[jira] [Updated] (RANGER-4346) Need to Change type of column resource_signature in table x_gds_shared_resource to TEXT

[Prashant Satam (Jira)]

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

Prashant Satam updated RANGER-4346:
---
Description: Need to change the type of 

> Need to Change type of column resource_signature in table 
> x_gds_shared_resource to TEXT
> ---
>
> Key: RANGER-4346
> URL: https://issues.apache.org/jira/browse/RANGER-4346
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Minor
>
> Need to change the type of 



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

[jira] [Created] (RANGER-4347) User name with "," spited in old Ranger admin UI .

[Dhaval Rajpara (Jira)]

Dhaval Rajpara created RANGER-4347:
--

 Summary: User name with "," spited in old Ranger admin UI .
 Key: RANGER-4347
 URL: https://issues.apache.org/jira/browse/RANGER-4347
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Reporter: Dhaval Rajpara
Assignee: Dhaval Rajpara


when using Ranger Audit filter to filter out the audit for a specific user:
Usually, if we input a username, it would be no issue, but if we input the user 
like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”.
We found that once we saved the audit filter policy, the user was split into 
“CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com”
It happens because Ranger UI recognize “,” to be separate items.

Same scenario is present in :
1) Security Zone Form 
2) Permission modules
3) Role Form




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

[jira] [Assigned] (RANGER-4346) Need to Change type of column resource_signature in table x_gds_shared_resource to TEXT

[Prashant Satam (Jira)]

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

Prashant Satam reassigned RANGER-4346:
--

Assignee: Prashant Satam

> Need to Change type of column resource_signature in table 
> x_gds_shared_resource to TEXT
> ---
>
> Key: RANGER-4346
> URL: https://issues.apache.org/jira/browse/RANGER-4346
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Minor
>




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

[jira] [Created] (RANGER-4346) Need to Change type of column resource_signature in table x_gds_shared_resource to TEXT

[Prashant Satam (Jira)]

Prashant Satam created RANGER-4346:
--

 Summary: Need to Change type of column resource_signature in table 
x_gds_shared_resource to TEXT
 Key: RANGER-4346
 URL: https://issues.apache.org/jira/browse/RANGER-4346
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Reporter: Prashant Satam






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