[jira] [Commented] (RANGER-2844) presto-server-333 can not show schemas/tables after integrated with Ranger master branch
[
https://issues.apache.org/jira/browse/RANGER-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126888#comment-17126888
]
Jie Zhang commented on RANGER-2844:
---
[~bolke], Hi Bolke, I saw you have worked on presto-server-333, any thoughts
on {color:#00875a}*show schemas/tables*{color} got access denied from ranger?
Thanks.
https://issues.apache.org/jira/browse/RANGER-2826
> presto-server-333 can not show schemas/tables after integrated with Ranger
> master branch
>
>
> Key: RANGER-2844
> URL: https://issues.apache.org/jira/browse/RANGER-2844
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
> Environment: Amazon Linux
>Reporter: Jie Zhang
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: got access denied for show command.png, no show
> command.png
>
>
> Integrated presto-server-333 with Ranger master branch, able to run
> use/select queries, but got access denied when running *{color:#00875a}show
> schemas/tables{color}*.
> I saw there is no {color:#00875a}*show*{color} command on ranger-ui
> (screenshot attached), is that why presto can not show schemas/tables? Any
> workaround? Thanks a lot.
>
> Error:
> {code:java}
> presto:default> use default;
> USE
> presto:default> show schemas;
> Query 20200604_192311_00023_sa7kt failed: Access Denied: Cannot show schemas:
> hivepresto:default> show tables;
> Query 20200604_192319_00024_sa7kt failed: Access Denied: Cannot show tables
> of schema hive.default
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2844) presto-server-333 can not show schemas/tables after integrated with Ranger master branch
[
https://issues.apache.org/jira/browse/RANGER-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Zhang updated RANGER-2844:
--
Priority: Major (was: Blocker)
> presto-server-333 can not show schemas/tables after integrated with Ranger
> master branch
>
>
> Key: RANGER-2844
> URL: https://issues.apache.org/jira/browse/RANGER-2844
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
> Environment: Amazon Linux
>Reporter: Jie Zhang
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: got access denied for show command.png, no show
> command.png
>
>
> Integrated presto-server-333 with Ranger master branch, able to run
> use/select queries, but got access denied when running *{color:#00875a}show
> schemas/tables{color}*.
> I saw there is no {color:#00875a}*show*{color} command on ranger-ui
> (screenshot attached), is that why presto can not show schemas/tables? Any
> workaround? Thanks a lot.
>
> Error:
> {code:java}
> presto:default> use default;
> USE
> presto:default> show schemas;
> Query 20200604_192311_00023_sa7kt failed: Access Denied: Cannot show schemas:
> hivepresto:default> show tables;
> Query 20200604_192319_00024_sa7kt failed: Access Denied: Cannot show tables
> of schema hive.default
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Review Request 72571: RANGER-2849: Allow Ranger to be configurable to not disclose server version
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72571/ --- Review request for ranger, Ankita Sinha, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-2849 https://issues.apache.org/jira/browse/RANGER-2849 Repository: ranger Description --- Allow Ranger to be configurable to not disclose server version Diffs - embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/EmbeddedServer.java dc931c25d security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 3eb47f932 Diff: https://reviews.apache.org/r/72571/diff/1/ Testing --- After getting error/exception ranger does not disclose server version if ranger.valve.errorreportvalve.showserverinfo set to false. When ranger.valve.errorreportvalve.showreport is set to false; it does not disclose exception message in response. Thanks, Mahesh Bandal
[jira] [Updated] (RANGER-2849) Allow Ranger to be configurable to not disclose server version
[ https://issues.apache.org/jira/browse/RANGER-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahesh Hanumant Bandal updated RANGER-2849: --- Attachment: RANGER-2849-V1.patch > Allow Ranger to be configurable to not disclose server version > -- > > Key: RANGER-2849 > URL: https://issues.apache.org/jira/browse/RANGER-2849 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.1.0 >Reporter: Mehul Parikh >Assignee: Mahesh Hanumant Bandal >Priority: Major > Fix For: 2.1.0 > > Attachments: RANGER-2849-V1.patch > > > Allow Ranger to be configurable to not disclose server version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2849) Allow Ranger to be configurable to not disclose server version
Mehul Parikh created RANGER-2849: Summary: Allow Ranger to be configurable to not disclose server version Key: RANGER-2849 URL: https://issues.apache.org/jira/browse/RANGER-2849 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 2.1.0 Reporter: Mehul Parikh Assignee: Mahesh Hanumant Bandal Fix For: 2.1.0 Allow Ranger to be configurable to not disclose server version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2845) Cleanup ozone service configurations
[
https://issues.apache.org/jira/browse/RANGER-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Shukla updated RANGER-2845:
Labels: ozone (was: ozone plugins)
> Cleanup ozone service configurations
>
>
> Key: RANGER-2845
> URL: https://issues.apache.org/jira/browse/RANGER-2845
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: Abhishek Shukla
>Priority: Minor
> Labels: ozone
>
> Creating this Jira for cleaning up/removing unused configs in ozone service.
> {noformat}
> dfs.datanode.kerberos.principal
> dfs.namenode.kerberos.principal
> dfs.secondary.namenode.kerberos.principal
> {noformat}
>
> Other configs like these [Are we consuming these or should these be removed?]:
> {noformat}
> Authorization Enabled
> Common Name for Certificate
> {noformat}
>
> Improvements:
> {noformat}
> Password config should only be shown in the UI or mandatory if Authentication
> Type is Simple?
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2847) Add support/Fix Test connection with Ozone service
[
https://issues.apache.org/jira/browse/RANGER-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Shukla updated RANGER-2847:
Labels: ozone (was: ozone plugins)
> Add support/Fix Test connection with Ozone service
> --
>
> Key: RANGER-2847
> URL: https://issues.apache.org/jira/browse/RANGER-2847
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: Abhishek Shukla
>Priority: Major
> Labels: ozone
>
> Currently, Test Connection with Ozone Service is failing with this error.
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/ozone/client/OzoneClientFactory.{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Shukla updated RANGER-2846: Labels: ozone (was: ozone plugins) > Add support for resource[volume, bucket, key] look up in ozone plugin > - > > Key: RANGER-2846 > URL: https://issues.apache.org/jira/browse/RANGER-2846 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.1.0 >Reporter: Abhishek Shukla >Priority: Major > Labels: ozone > > The task to add support for resource [volume, bucket, key] lookup while > creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2848) Update Ozone service definition resource type volume
Abhishek Shukla created RANGER-2848:
---
Summary: Update Ozone service definition resource type volume
Key: RANGER-2848
URL: https://issues.apache.org/jira/browse/RANGER-2848
Project: Ranger
Issue Type: Bug
Components: plugins
Affects Versions: 2.1.0
Reporter: Abhishek Shukla
* Set {{isRecursive}} flag to false in ozone service def for resource type
Volume
* We need to add the {{isRecursive}} flag to key resource [as a key can be a
directory in ozone]
* Can we also add the {{isExcludes}} flag to the volume resource as part of
this change?
* _Improvement_: If {{isExcludes}} is set to True for high-level resources
[volume, bucket], the lower-level resources [bucket, key] should not be shown
in the UI?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-2847) Add support/Fix Test connection with Ozone service
Abhishek Shukla created RANGER-2847:
---
Summary: Add support/Fix Test connection with Ozone service
Key: RANGER-2847
URL: https://issues.apache.org/jira/browse/RANGER-2847
Project: Ranger
Issue Type: Bug
Components: plugins
Affects Versions: 2.1.0
Reporter: Abhishek Shukla
Currently, Test Connection with Ozone Service is failing with this error.
{noformat}
java.lang.NoClassDefFoundError:
org/apache/hadoop/ozone/client/OzoneClientFactory.{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
Abhishek Shukla created RANGER-2846: --- Summary: Add support for resource[volume, bucket, key] look up in ozone plugin Key: RANGER-2846 URL: https://issues.apache.org/jira/browse/RANGER-2846 Project: Ranger Issue Type: Task Components: plugins Affects Versions: 2.1.0 Reporter: Abhishek Shukla The task to add support for resource [volume, bucket, key] lookup while creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2845) Cleanup ozone service configurations
Abhishek Shukla created RANGER-2845:
---
Summary: Cleanup ozone service configurations
Key: RANGER-2845
URL: https://issues.apache.org/jira/browse/RANGER-2845
Project: Ranger
Issue Type: Improvement
Components: plugins
Affects Versions: 2.1.0
Reporter: Abhishek Shukla
Creating this Jira for cleaning up/removing unused configs in ozone service.
{noformat}
dfs.datanode.kerberos.principal
dfs.namenode.kerberos.principal
dfs.secondary.namenode.kerberos.principal
{noformat}
Other configs like these [Are we consuming these or should these be removed?]:
{noformat}
Authorization Enabled
Common Name for Certificate
{noformat}
Improvements:
{noformat}
Password config should only be shown in the UI or mandatory if Authentication
Type is Simple?
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
