You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by prabhjyotsingh <gi...@git.apache.org> on 2016/07/19 16:40:16 UTC

[GitHub] zeppelin pull request #1205: [ZEPPELIN-1212] User impersonation support in J...

GitHub user prabhjyotsingh opened a pull request:

    https://github.com/apache/zeppelin/pull/1205

    [ZEPPELIN-1212] User impersonation support in JDBC interpreter for Hive\u2026

    ### What is this PR for?
    Add impersonation support to JDBC interpreters, in addition to Kerberos Authentication to improve auditability in all JDBC interpreters.
    
    
    
    ### What type of PR is it?
    [Bug Fix | Improvement]
    
    
    ### What is the Jira issue?
    * [ZEPPELIN-1212](https://issues.apache.org/jira/browse/ZEPPELIN-1212)
    
    ### How should this be tested?
    In JDBC interpreter setting add following properties
    
     - zeppelin.jdbc.auth.type = KERBEROS
     - zeppelin.jdbc.principal = principal value
     - zeppelin.jdbc.keytab.location = keytab location
     - enable shiro authentication via shiro.ini
    
    Now try and run any of hive's query (say show tables) it should return with valid results/errors depending on user permission.
    
    ### Questions:
    * Does the licenses files need update? n/a
    * Is there breaking changes for older versions? n/a
    * Does this needs documentation? n/a
    
    \u2026 and Phoenix(Others)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-1212

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1205.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1205
    
----
commit 66824a07445208b4ab4aa407c66abbc488b35eec
Author: Prabhjyot Singh <pr...@gmail.com>
Date:   2016-07-19T16:36:16Z

    ZEPPELIN-1212 User impersonation support in JDBC interpreter for Hive and Phoenix(Others)

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1205: [ZEPPELIN-1212] User impersonation support in JDBC

Posted by prabhjyotsingh <gi...@git.apache.org>.
Github user prabhjyotsingh commented on the issue:

    https://github.com/apache/zeppelin/pull/1205
  
    Merging this if no more discussion.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1205: [ZEPPELIN-1212] User impersonation support in J...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/zeppelin/pull/1205


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1205: [ZEPPELIN-1212] User impersonation support in JDBC

Posted by rconline <gi...@git.apache.org>.
Github user rconline commented on the issue:

    https://github.com/apache/zeppelin/pull/1205
  
    LGTM, at some stage we should start thinking about connection pooling. But that can be a different PR. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---