GitHub user astroshim opened a pull request:
https://github.com/apache/zeppelin/pull/1539
[ZEPPELIN-1567] Let JDBC interpreter use user credential information.
### What is this PR for?
This PR is for the multi-tenant of JDBC Interpreter.
User can create a user/password for JDBC account at the [Credential
page](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/security/datasource_authorization.html).
The `Entity` of `Credential` is match with JDBC interpreter group name.
If the account for JDBC is not setted in the `Interpreter property` then
use `Credential`'s.
### What type of PR is it?
Improvement
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1567
### How should this be tested?
Please refer to testMultiTenant() of JDBCInterpreterTest/
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astroshim/zeppelin jdbc-impersonation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1539.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 #1539
----
commit 373d5f1018488ab435d817551f2b628258cc42b9
Author: astroshim <hss...@nflabs.com>
Date: 2016-10-18T10:53:26Z
pass replName to Interpreter and use credential info for jdbc auth.
commit 3dafdf017c9b1cdb04565d8132e48a18942ea971
Author: astroshim <hss...@nflabs.com>
Date: 2016-10-18T15:14:59Z
add testcase
commit 91619374be06fadd9608d02a7e13d347ad9e0a07
Author: astroshim <hss...@nflabs.com>
Date: 2016-10-18T15:15:40Z
clean code
commit 722e333fe47c007a0252f744d5a3173613bed50f
Author: astroshim <hss...@nflabs.com>
Date: 2016-10-18T16:25:59Z
change testcase name
----
---
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.
---
