GitHub user prasadwagle reopened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/860

    [ZEPPELIN-828] Use individual user credentials for data source 
authentication

    ### What is this PR for?
    The purpose of this pull request is to allow users to use their own 
credentials to authenticate with data sources.
    It contains the following:
    - web UI and rest API to let users input their credentials
    - changes to AuthenticationInfo to add data source credentials
    - changes to Paragraph to set data source credentials in AuthenticationInfo
    - changes to HiveInterpreter to use the user credentials and simplification 
to use a new connection for every query. We made this change since we found an 
issue with closed vertica connections. Since we are using HiveInterpreter for 
analytics, the cost of creating a new connection is small compared to query 
execution. We don't have to merge this change into master.
    
    ### What type of PR is it?
    Feature
    
    ### Todos
    * [x] - Save user credentials in a file
    * [x] - Do not persist AuthenticationInfo in paragraph since it contains 
sensitive information
    * [ ] - Add tests
    * [ ] - Add documentation
    
    ### What is the Jira issue?
    [ZEPPELIN-828] (https://issues.apache.org/jira/browse/ZEPPELIN-828)
    
    ### How should this be tested?
    1. In conf/shiro.ini, use /** = authc
    1. Login to Zeppelin
    2. Enter credentials for a data source
    3. Check if the interpreter is using the correct credentials
    
    ### Screenshots (if appropriate)
    https://gfycat.com/LiquidGentleKatydid
    
    ### Questions:
    * Does this needs documentation? Yes.
    


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

    $ git pull https://github.com/prasadwagle/incubator-zeppelin ZEPPELIN-828

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

    https://github.com/apache/incubator-zeppelin/pull/860.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 #860
    
----
commit 215d15464379479c3d6d923a675a0cb16e102bea
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-04-27T20:10:00Z

    Use individual user credentials for data source authentication

commit 970b3e6bf39dfc99f0056e5a80ddabc400e2038f
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-10T18:31:08Z

    Pass all user credentials to the interpreter

commit 1c4e831da524fdee88a0b37e03cd2e4f1162471e
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-10T20:43:33Z

    Persist user info instead of authentication info in paragraph

commit a20567befc99e18effaf0aba31b68e4f92e87972
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-10T22:02:05Z

    Persist credentials depending on conf setting

commit 0d7c913456f88cf0ba342627b672651bdea0b3d8
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-11T00:15:07Z

    Fix checkstyle error, Update Data Source Authorization section in docs

commit 731d0c5420d505d2da8a3aab51d3cc1ea43c98ec
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-11T00:28:36Z

    Remove vertica dependency from hive/pom.xml

commit 69fbd8d544a7dbced507de093ebe72349244e9c1
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-11T21:24:51Z

    Revert changes to HiveInterpreter, Update tests

commit dbdb1f8e2288179a7b4a85c82711a1eebaff0b03
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-11T23:48:30Z

    Added conf/credentials.json to .gitignore

commit cedf8f55ea079ac58ce59b88a86a9935c2976cb8
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-21T23:00:08Z

    Use a more general term 'entity' instead of 'datasource'

commit 46440ed40a4fd8dfaaa98dc30a791313d7d0d7b1
Author: Prasad Wagle <pwa...@twitter.com>
Date:   2016-05-24T23:01:19Z

    Use LOG.error(msg, e)

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to