mirror of
https://github.com/apache/zeppelin
synced 2026-05-24 09:38:26 +00:00
Fixed typo in _navigation.html and updated interpreter_authorization.md
This commit is contained in:
parent
6c89dbe93d
commit
1ac076e1a8
2 changed files with 11 additions and 5 deletions
|
|
@ -58,7 +58,7 @@
|
|||
<li>
|
||||
<a href="#" data-toggle="dropdown" class="dropdown-toggle">Security<b class="caret"></b></a>
|
||||
<ul class="dropdown-menu">
|
||||
<li><a href="{{BASE_PATH}}/security/overviwe.html">Overview</a></li>
|
||||
<li><a href="{{BASE_PATH}}/security/overview.html">Overview</a></li>
|
||||
<li><a href="{{BASE_PATH}}/security/authentication.html#html">Authentication</a></li>
|
||||
<li><a href="{{BASE_PATH}}/security/notebook_authorization.html">Notebook Authorization</a></li>
|
||||
<li><a href="{{BASE_PATH}}/security/interpreter_authorization.html">Interpreter Authorization</a></li>
|
||||
|
|
|
|||
|
|
@ -17,12 +17,18 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
-->
|
||||
# Zeppelin Interpreter Authorization
|
||||
# Zeppelin Interpreter and Data Source Authorization
|
||||
|
||||
The Interpreter authorization problem is more complex. Different interpreters require different strategies.
|
||||
## Interpreter Authorization
|
||||
|
||||
Interpreter authorization involves permissions like creating an interpreter and execution queries using it.
|
||||
|
||||
## Data Source Authorization
|
||||
|
||||
Data source authorization involves authenticating to the data source like a Mysql database and letting it determine user permissions.
|
||||
|
||||
For the Hive interpreter, we need to maintain per-user connection pools.
|
||||
The interpreter method takes the user string as parameter and executes the jdbc call using a connection in the user's connection pool.
|
||||
The interpret method takes the user string as parameter and executes the jdbc call using a connection in the user's connection pool.
|
||||
|
||||
In case of Presto, we don't need password if the Presto DB server runs backend code using HDFS authorization for the user.
|
||||
For databases like Vertica and Mysql we would have to store password information for users.
|
||||
For databases like Vertica and Mysql we have to store password information for users.
|
||||
|
|
|
|||
Loading…
Reference in a new issue