[jira] [Created] (RANGER-4782) Implement best coding practices for validating service configs
Sanket Shelar created RANGER-4782: - Summary: Implement best coding practices for validating service configs Key: RANGER-4782 URL: https://issues.apache.org/jira/browse/RANGER-4782 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Implement best coding practices for validating service configs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4690) Access Audits - Resource policy version used for mask policy leading to Error page
[ https://issues.apache.org/jira/browse/RANGER-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4690: -- Attachment: 0001-RANGER-4690.patch > Access Audits - Resource policy version used for mask policy leading to Error > page > -- > > Key: RANGER-4690 > URL: https://issues.apache.org/jira/browse/RANGER-4690 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: suja s >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4690.patch > > > Create a ranger hive policy for user u1 to access table t1. > Create table t1 and add data > Edit the policy to have multiple versions. Polocy version is now 'y' > Create a ranger hive masking policy for one of the columns of t1. > Edit the policy to have multiple versions. Policy version is less than 'y' > example, if resource policy version is 5, have masking policy version as 4. > Try insert command on t1. It fails now as there is a masking policy. > Inspect access audits on ranger admin UI. Click on policyid for the denied > audit for insert > CURRENT BEHAVIOUR: > Access audits show version of resource policy for mask policy id, so querying > for policy details leads to data not found error page > Policy cache json file on plugin side has the right version, x_policy table > has the right entries for corresponding masking policy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4690) Access Audits - Resource policy version used for mask policy leading to Error page
[ https://issues.apache.org/jira/browse/RANGER-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar reassigned RANGER-4690: - Assignee: Sanket Shelar > Access Audits - Resource policy version used for mask policy leading to Error > page > -- > > Key: RANGER-4690 > URL: https://issues.apache.org/jira/browse/RANGER-4690 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: suja s >Assignee: Sanket Shelar >Priority: Major > > Create a ranger hive policy for user u1 to access table t1. > Create table t1 and add data > Edit the policy to have multiple versions. Polocy version is now 'y' > Create a ranger hive masking policy for one of the columns of t1. > Edit the policy to have multiple versions. Policy version is less than 'y' > example, if resource policy version is 5, have masking policy version as 4. > Try insert command on t1. It fails now as there is a masking policy. > Inspect access audits on ranger admin UI. Click on policyid for the denied > audit for insert > CURRENT BEHAVIOUR: > Access audits show version of resource policy for mask policy id, so querying > for policy details leads to data not found error page > Policy cache json file on plugin side has the right version, x_policy table > has the right entries for corresponding masking policy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4487) HSTS header missing from unsecured API in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4487: -- Attachment: 0002-RANGER-4487.patch > HSTS header missing from unsecured API in Ranger Admin > -- > > Key: RANGER-4487 > URL: https://issues.apache.org/jira/browse/RANGER-4487 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0002-RANGER-4487.patch > > > Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4487) HSTS header missing from unsecured API in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4487: -- Attachment: (was: 0001-RANGER-4487.patch) > HSTS header missing from unsecured API in Ranger Admin > -- > > Key: RANGER-4487 > URL: https://issues.apache.org/jira/browse/RANGER-4487 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0002-RANGER-4487.patch > > > Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4602) Upgrade Tomcat to 8.5.96 in all Ranger services
Sanket Shelar created RANGER-4602: - Summary: Upgrade Tomcat to 8.5.96 in all Ranger services Key: RANGER-4602 URL: https://issues.apache.org/jira/browse/RANGER-4602 Project: Ranger Issue Type: Task Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Upgrade Tomcat to 8.5.96 in all Ranger services -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4520) Both usersync/tagsync instances becoming active and syncing users/tags
[ https://issues.apache.org/jira/browse/RANGER-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4520: -- Attachment: 0001-RANGER-4520.patch > Both usersync/tagsync instances becoming active and syncing users/tags > -- > > Key: RANGER-4520 > URL: https://issues.apache.org/jira/browse/RANGER-4520 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: suja s >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4520.patch > > > Both usersync/tagsync instances becoming active and syncing users/tags in the > following scenario > Scenario: > Bring up 2 instances of UserSync so that one is active and other is passive > Cluster has 3 zk instances, stop 2 zk servers so that there is no quorum > Both usersync instances fail to establish Zk connection > Start both zk servers > Both usersync instances have transitioned to active and started performing > usersync > Same issue exists for tagsync also > Test: > Add user u1 to host1 > Add user u2 to host2 > Both users are synced and available on ranger admin side. > Usersync audits show details of both users synced > EXPECTED BEHAVIOUR: > In case of usersync/tagsync running in HA mode, there should be only 1 > instance active at any point of time > CURRENT BEHAVIOUR: > After zk goes down and is back functional, more than 1 usersync/tagsync > instance becoming active -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4520) Both usersync/tagsync instances becoming active and syncing users/tags
[ https://issues.apache.org/jira/browse/RANGER-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar reassigned RANGER-4520: - Assignee: Sanket Shelar > Both usersync/tagsync instances becoming active and syncing users/tags > -- > > Key: RANGER-4520 > URL: https://issues.apache.org/jira/browse/RANGER-4520 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: suja s >Assignee: Sanket Shelar >Priority: Major > > Both usersync/tagsync instances becoming active and syncing users/tags in the > following scenario > Scenario: > Bring up 2 instances of UserSync so that one is active and other is passive > Cluster has 3 zk instances, stop 2 zk servers so that there is no quorum > Both usersync instances fail to establish Zk connection > Start both zk servers > Both usersync instances have transitioned to active and started performing > usersync > Same issue exists for tagsync also > Test: > Add user u1 to host1 > Add user u2 to host2 > Both users are synced and available on ranger admin side. > Usersync audits show details of both users synced > EXPECTED BEHAVIOUR: > In case of usersync/tagsync running in HA mode, there should be only 1 > instance active at any point of time > CURRENT BEHAVIOUR: > After zk goes down and is back functional, more than 1 usersync/tagsync > instance becoming active -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4482) Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services
[ https://issues.apache.org/jira/browse/RANGER-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar resolved RANGER-4482. --- Resolution: Fixed > Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services > --- > > Key: RANGER-4482 > URL: https://issues.apache.org/jira/browse/RANGER-4482 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4482.patch > > > Tomcat needs be upgraded to 8.5.94 to address the below CVE. > CVE-2023-45648 > [https://nvd.nist.gov/vuln/detail/CVE-2023-45648] > CVE-2023-42795 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42795] > CVE-2023-42794 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42794] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4504) HBase shell revoke command failed with 'HTTP 400 Error: processSecureRevokeRequest processing failed'
[ https://issues.apache.org/jira/browse/RANGER-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4504: -- Attachment: 0001-RANGER-4504.patch > HBase shell revoke command failed with 'HTTP 400 Error: > processSecureRevokeRequest processing failed' > - > > Key: RANGER-4504 > URL: https://issues.apache.org/jira/browse/RANGER-4504 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4504.patch > > > Steps to reproduce: > Case 1 : > Grant access request from shell command > Revoke access twice > Case 2 : > Grant access to user1 from shell command > revoke access from user2 from shell command > Case 3 : > Ranger policy created at Group/Role access level > Revoke access request for user belongs to Group/Roles from shell command > Case 4 : > Grant access to user with Table from shell command > revoke access from user without Table from shell command -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4487) HSTS header missing from unsecured API in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4487: -- Attachment: 0001-RANGER-4487.patch > HSTS header missing from unsecured API in Ranger Admin > -- > > Key: RANGER-4487 > URL: https://issues.apache.org/jira/browse/RANGER-4487 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4487.patch > > > Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4504) HBase shell revoke command failed with 'HTTP 400 Error: processSecureRevokeRequest processing failed'
Sanket Shelar created RANGER-4504: - Summary: HBase shell revoke command failed with 'HTTP 400 Error: processSecureRevokeRequest processing failed' Key: RANGER-4504 URL: https://issues.apache.org/jira/browse/RANGER-4504 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Steps to reproduce: Case 1 : Grant access request from shell command Revoke access twice Case 2 : Grant access to user1 from shell command revoke access from user2 from shell command Case 3 : Ranger policy created at Group/Role access level Revoke access request for user belongs to Group/Roles from shell command Case 4 : Grant access to user with Table from shell command revoke access from user without Table from shell command -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4488) HSTS header missing from unsecured API in Ranger Tagsync and Usersync
Sanket Shelar created RANGER-4488: - Summary: HSTS header missing from unsecured API in Ranger Tagsync and Usersync Key: RANGER-4488 URL: https://issues.apache.org/jira/browse/RANGER-4488 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4487) HSTS header missing from unsecured API in Ranger Admin
Sanket Shelar created RANGER-4487: - Summary: HSTS header missing from unsecured API in Ranger Admin Key: RANGER-4487 URL: https://issues.apache.org/jira/browse/RANGER-4487 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Currently for unsecured APIs, HSTS header are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4482) Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services
[ https://issues.apache.org/jira/browse/RANGER-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4482: -- Attachment: 0001-RANGER-4482.patch > Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services > --- > > Key: RANGER-4482 > URL: https://issues.apache.org/jira/browse/RANGER-4482 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4482.patch > > > Tomcat needs be upgraded to 8.5.94 to address the below CVE. > CVE-2023-45648 > [https://nvd.nist.gov/vuln/detail/CVE-2023-45648] > CVE-2023-42795 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42795] > CVE-2023-42794 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42794] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4482) Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services
Sanket Shelar created RANGER-4482: - Summary: Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services Key: RANGER-4482 URL: https://issues.apache.org/jira/browse/RANGER-4482 Project: Ranger Issue Type: Task Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Tomcat needs be upgraded to 8.5.94 to address the below CVE. CVE-2023-45648 [https://nvd.nist.gov/vuln/detail/CVE-2023-45648] CVE-2023-42795 [https://nvd.nist.gov/vuln/detail/CVE-2023-42795] CVE-2023-42794 [https://nvd.nist.gov/vuln/detail/CVE-2023-42794] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4458) Ranger Usersync - Convert to Web Application
Sanket Shelar created RANGER-4458: - Summary: Ranger Usersync - Convert to Web Application Key: RANGER-4458 URL: https://issues.apache.org/jira/browse/RANGER-4458 Project: Ranger Issue Type: New Feature Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Convert Ranger UserSync to Web Application -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4453) Exception while calling solr api when ranger authorisation is disabled for solr
[
https://issues.apache.org/jira/browse/RANGER-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanket Shelar updated RANGER-4453:
--
Attachment: 0001-RANGER-4453.patch
> Exception while calling solr api when ranger authorisation is disabled for
> solr
> ---
>
> Key: RANGER-4453
> URL: https://issues.apache.org/jira/browse/RANGER-4453
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sanket Shelar
>Assignee: Sanket Shelar
>Priority: Major
> Attachments: 0001-RANGER-4453.patch
>
>
> Disable ranger authorisation for solr.
> kinit using systest user
> run curl -i -k --negotiate -u :
> [https://host:8995/solr/test_collection_01/select] -d 'q={*}:{*}'
> we get 500 server error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4453) Exception while calling solr api when ranger authorisation is disabled for solr
[
https://issues.apache.org/jira/browse/RANGER-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanket Shelar updated RANGER-4453:
--
Description:
Disable ranger authorisation for solr.
kinit using systest user
run curl -i -k --negotiate -u :
[https://host:8995/solr/test_collection_01/select] -d 'q={*}:{*}'
we get 500 server error
> Exception while calling solr api when ranger authorisation is disabled for
> solr
> ---
>
> Key: RANGER-4453
> URL: https://issues.apache.org/jira/browse/RANGER-4453
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sanket Shelar
>Assignee: Sanket Shelar
>Priority: Major
>
> Disable ranger authorisation for solr.
> kinit using systest user
> run curl -i -k --negotiate -u :
> [https://host:8995/solr/test_collection_01/select] -d 'q={*}:{*}'
>
> we get 500 server error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4453) Exception while calling solr api when ranger authorisation is disabled for solr
[
https://issues.apache.org/jira/browse/RANGER-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanket Shelar updated RANGER-4453:
--
Description:
Disable ranger authorisation for solr.
kinit using systest user
run curl -i -k --negotiate -u :
[https://host:8995/solr/test_collection_01/select] -d 'q={*}:{*}'
we get 500 server error
was:
Disable ranger authorisation for solr.
kinit using systest user
run curl -i -k --negotiate -u :
[https://host:8995/solr/test_collection_01/select] -d 'q={*}:{*}'
we get 500 server error
> Exception while calling solr api when ranger authorisation is disabled for
> solr
> ---
>
> Key: RANGER-4453
> URL: https://issues.apache.org/jira/browse/RANGER-4453
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Sanket Shelar
>Assignee: Sanket Shelar
>Priority: Major
>
> Disable ranger authorisation for solr.
> kinit using systest user
> run curl -i -k --negotiate -u :
> [https://host:8995/solr/test_collection_01/select] -d 'q={*}:{*}'
> we get 500 server error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4453) Exception while calling solr api when ranger authorisation is disabled for solr
Sanket Shelar created RANGER-4453: - Summary: Exception while calling solr api when ranger authorisation is disabled for solr Key: RANGER-4453 URL: https://issues.apache.org/jira/browse/RANGER-4453 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4348) Filter audits for cc_metric_reporter user on Kafka service repo
[ https://issues.apache.org/jira/browse/RANGER-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4348: -- Attachment: 0001-RANGER-4348.patch > 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: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4348.patch > > > 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-4348) Filter audits for cc_metric_reporter user on Kafka service repo
[ https://issues.apache.org/jira/browse/RANGER-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4348: -- Attachment: (was: 0001-RANGER-4348.patch) > 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: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4348.patch > > > 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-3346) Ranger Solr Plugin sends audits with PKI auth instead of Kerberos
[ https://issues.apache.org/jira/browse/RANGER-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-3346: -- Attachment: 0001-RANGER-3346.patch > Ranger Solr Plugin sends audits with PKI auth instead of Kerberos > - > > Key: RANGER-3346 > URL: https://issues.apache.org/jira/browse/RANGER-3346 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Geza Nagy >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-3346.patch > > > SolrAuditDestination class connects to Solr by building client with > HttpClientUtil (from SolrJ library). > It's fine except in case of Solr Ranger Plugin. The Solr server uses the > SolrJ lib as well for communication among its nodes and sets static/global > configuration inside the HttpClientUtil which makes the SolrAuditDestination > class's client to misbehave as sending the audits request with a header which > forces the authentication to PKI. Prior to Solr 8.8 it leaded to only warning > level Exceptions but after this version this will cause failure when sending > audits. > Relevant Solr JIRA about changing the implementation of HttpClientUtil class: > https://issues.apache.org/jira/browse/SOLR-15388 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-3346) Ranger Solr Plugin sends audits with PKI auth instead of Kerberos
[ https://issues.apache.org/jira/browse/RANGER-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar reassigned RANGER-3346: - Assignee: Sanket Shelar > Ranger Solr Plugin sends audits with PKI auth instead of Kerberos > - > > Key: RANGER-3346 > URL: https://issues.apache.org/jira/browse/RANGER-3346 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Geza Nagy >Assignee: Sanket Shelar >Priority: Major > > SolrAuditDestination class connects to Solr by building client with > HttpClientUtil (from SolrJ library). > It's fine except in case of Solr Ranger Plugin. The Solr server uses the > SolrJ lib as well for communication among its nodes and sets static/global > configuration inside the HttpClientUtil which makes the SolrAuditDestination > class's client to misbehave as sending the audits request with a header which > forces the authentication to PKI. Prior to Solr 8.8 it leaded to only warning > level Exceptions but after this version this will cause failure when sending > audits. > Relevant Solr JIRA about changing the implementation of HttpClientUtil class: > https://issues.apache.org/jira/browse/SOLR-15388 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4421) Ranger - Upgrade Tomcat to 8.5.93/9.0.80 due to CVE-2023-41080
[
https://issues.apache.org/jira/browse/RANGER-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanket Shelar updated RANGER-4421:
--
Attachment: 0001-RANGER-4421.patch
> Ranger - Upgrade Tomcat to 8.5.93/9.0.80 due to CVE-2023-41080
> --
>
> Key: RANGER-4421
> URL: https://issues.apache.org/jira/browse/RANGER-4421
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Reporter: Sanket Shelar
>Assignee: Sanket Shelar
>Priority: Major
> Attachments: 0001-RANGER-4421.patch
>
>
> URL Redirection to Untrusted Site ('Open Redirect') vulnerability in FORM
> authentication feature Apache Tomcat.This issue affects Apache Tomcat: from
> 11.0.0-M1 through 11.0.0-M10, from 10.1.0-M1 through 10.0.12, from 9.0.0-M1
> through 9.0.79 and from 8.5.0 through 8.5.92. The vulnerability is limited to
> the ROOT (default) web application.
> CVSSv3 Score:- 6.1(Medium)
> [https://nvd.nist.gov/vuln/detail/CVE-2023-41080]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4421) Ranger - Upgrade Tomcat to 8.5.93/9.0.80 due to CVE-2023-41080
Sanket Shelar created RANGER-4421:
-
Summary: Ranger - Upgrade Tomcat to 8.5.93/9.0.80 due to
CVE-2023-41080
Key: RANGER-4421
URL: https://issues.apache.org/jira/browse/RANGER-4421
Project: Ranger
Issue Type: Task
Components: Ranger
Reporter: Sanket Shelar
Assignee: Sanket Shelar
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in FORM
authentication feature Apache Tomcat.This issue affects Apache Tomcat: from
11.0.0-M1 through 11.0.0-M10, from 10.1.0-M1 through 10.0.12, from 9.0.0-M1
through 9.0.79 and from 8.5.0 through 8.5.92. The vulnerability is limited to
the ROOT (default) web application.
CVSSv3 Score:- 6.1(Medium)
[https://nvd.nist.gov/vuln/detail/CVE-2023-41080]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4373) Deleting a role which is already present in policy is giving incorrect message.
[ https://issues.apache.org/jira/browse/RANGER-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4373: -- Attachment: 0001-RANGER-4373.patch > Deleting a role which is already present in policy is giving incorrect > message. > --- > > Key: RANGER-4373 > URL: https://issues.apache.org/jira/browse/RANGER-4373 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4373.patch > > > In case if a role is already present in policy and we try to delete the role > then we are getting message as "data not found" instead of "Role can not be > deleted as it is referenced in one or more policies" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4373) Deleting a role which is already present in policy is giving incorrect message.
[ https://issues.apache.org/jira/browse/RANGER-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4373: -- Attachment: (was: 0001-RANGER-4373.patch) > Deleting a role which is already present in policy is giving incorrect > message. > --- > > Key: RANGER-4373 > URL: https://issues.apache.org/jira/browse/RANGER-4373 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > > In case if a role is already present in policy and we try to delete the role > then we are getting message as "data not found" instead of "Role can not be > deleted as it is referenced in one or more policies" -- 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: 0002-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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: (was: 0001-RANGER-4285.patch) > 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: 0002-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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: 0002-RANGER-4285.patch > 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: 0002-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)
[jira] [Reopened] (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 reopened RANGER-4285: --- > 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)
[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)
[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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: 0001-RANGER-4285.patch > 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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: (was: 0003-RANGER-4285.patch) > 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)
[jira] [Updated] (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 updated RANGER-4343: -- Attachment: (was: 0002-RANGER-4343.patch) > 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)
[jira] [Updated] (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 updated RANGER-4343: -- Attachment: 0001-RANGER-4343.patch > 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)
[jira] [Updated] (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 updated RANGER-4343: -- Attachment: 0002-RANGER-4343.patch > 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: 0002-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)
[jira] [Updated] (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 updated RANGER-4343: -- Attachment: (was: 0001-RANGER-4343.patch) > 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: 0002-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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: (was: 0003-RANGER-4285.patch) > 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: 0003-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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: 0003-RANGER-4285.patch > 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: 0003-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)
[jira] [Updated] (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 updated RANGER-4290: -- Attachment: 0001-RANGER-4290.patch > 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] [Updated] (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 updated RANGER-4290: -- Attachment: (was: 0002-RANGER-4290.patch) > 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 > > 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-4344) Export roles and import roles API should return proper error message incase of requests with invalid permissions
[ https://issues.apache.org/jira/browse/RANGER-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar resolved RANGER-4344. --- Resolution: Duplicate > Export roles and import roles API should return proper error message incase > of requests with invalid permissions > > > Key: RANGER-4344 > URL: https://issues.apache.org/jira/browse/RANGER-4344 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > > Changing the response content to be a message which indicates that the user > does > not have the required permissions in case Whenever a non-admin user invokes > the export/import role api. The status code of the request > is 403 (as expected), -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4373) Deleting a role which is already present in policy is giving incorrect message.
[ https://issues.apache.org/jira/browse/RANGER-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4373: -- Attachment: 0001-RANGER-4373.patch > Deleting a role which is already present in policy is giving incorrect > message. > --- > > Key: RANGER-4373 > URL: https://issues.apache.org/jira/browse/RANGER-4373 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4373.patch > > > In case if a role is already present in policy and we try to delete the role > then we are getting message as "data not found" instead of "Role can not be > deleted as it is referenced in one or more policies" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4373) Deleting a role which is already present in policy is giving incorrect message.
Sanket Shelar created RANGER-4373: - Summary: Deleting a role which is already present in policy is giving incorrect message. Key: RANGER-4373 URL: https://issues.apache.org/jira/browse/RANGER-4373 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar In case if a role is already present in policy and we try to delete the role then we are getting message as "data not found" instead of "Role can not be deleted as it is referenced in one or more policies" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: (was: 0001-RANGER-4285.patch) > 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: 0003-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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: 0003-RANGER-4285.patch > 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: 0003-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)
[jira] [Updated] (RANGER-4348) Filter audits for cc_metric_reporter user on Kafka service repo
[ https://issues.apache.org/jira/browse/RANGER-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Shelar updated RANGER-4348: -- Attachment: 0001-RANGER-4348.patch > 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 > Attachments: 0001-RANGER-4348.patch > > > 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-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 updated RANGER-4343: -- Attachment: 0001-RANGER-4343.patch > 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)
[jira] [Created] (RANGER-4344) Export roles and import roles API should return proper error message incase of requests with invalid permissions
Sanket Shelar created RANGER-4344: - Summary: Export roles and import roles API should return proper error message incase of requests with invalid permissions Key: RANGER-4344 URL: https://issues.apache.org/jira/browse/RANGER-4344 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Changing the response content to be a message which indicates that the user does not have the required permissions in case Whenever a non-admin user invokes the export/import role api. The status code of the request is 403 (as expected), -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4343) Atlas default policy is showing 2 "admin" users in policy items
Sanket Shelar created RANGER-4343: - Summary: 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 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)
[jira] [Updated] (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 updated RANGER-4290: -- Attachment: (was: RANGER-4290.1.patch) > 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: 0002-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] [Updated] (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 updated RANGER-4290: -- Attachment: 0002-RANGER-4290.patch > 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: 0002-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] [Updated] (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 updated RANGER-4290: -- Attachment: RANGER-4290.1.patch > 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: RANGER-4290.1.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] [Updated] (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 updated RANGER-4285: -- Attachment: 0001-RANGER-4285.patch > 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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: (was: RANGER-4285.patch) > 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)
[jira] [Updated] (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 updated RANGER-4285: -- Attachment: RANGER-4285.patch > 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: 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)
[jira] [Created] (RANGER-4290) Adding uiHint attribute in policy condition
Sanket Shelar created RANGER-4290: - Summary: 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 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] [Created] (RANGER-4285) Ranger Java Patch for adding uiHint in policy condition for upgrade scenario
Sanket Shelar created RANGER-4285: - Summary: 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 Ranger Java Patch for adding uiHint in policy condition for upgrade scenario -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4153) Ranger Tagsync - Convert to Web Application
Sanket Shelar created RANGER-4153: - Summary: Ranger Tagsync - Convert to Web Application Key: RANGER-4153 URL: https://issues.apache.org/jira/browse/RANGER-4153 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Sanket Shelar Assignee: Sanket Shelar Convert Ranger Tag Sync to Web Application -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-3932) Modifying the security zone name should also change the resourcesignature of their policy.
sanket shelar created RANGER-3932: - Summary: Modifying the security zone name should also change the resourcesignature of their policy. Key: RANGER-3932 URL: https://issues.apache.org/jira/browse/RANGER-3932 Project: Ranger Issue Type: Bug Components: Ranger Reporter: sanket shelar After updating the security zone name it should also change the resource signature of the policies under the security zone -- This message was sent by Atlassian Jira (v8.20.10#820010)
