[ 
https://issues.apache.org/jira/browse/TEZ-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589122#comment-15589122
 ] 

Alexandre Linte commented on TEZ-3418:
--------------------------------------

Hi [~hitesh],

Sorry for the late response. 

The idea here was to implement a Kerberos mechanism system inside the tez-ui 
configuration. Something similar to the Hadoop timeline service as below: 
{noformat}
<property>
    <name>yarn.timeline-service.http-authentication.type</name>
    <value>kerberos</value>
</property>

<property>
    
<name>yarn.timeline-service.http-authentication.simple.anonymous.allowed</name>
    <value>false</value>
</property>

<property>
    <name>yarn.timeline-service.http-authentication.kerberos.principal</name>
    <value>HTTP/[email protected]</value>
</property>

<property>
    <name>yarn.timeline-service.http-authentication.kerberos.keytab</name>
    <value>/opt/application/Hadoop/current/keytabs/hadoop.keytab</value>
</property>

<property>
    <name>yarn.timeline-service.principal</name>
    <value>tl/[email protected]</value>
</property>

<property>
    <name>yarn.timeline-service.keytab</name>
    <value>/opt/application/Hadoop/current/keytabs/yarn.keytab</value>
</property>
{noformat}

Hosting the ui war within the timeline server could be another idea, but I'm 
not sure it would work.

Today I didn't try to implement something.  

> Tez UI/UI2 doesn't support kerberized cluster
> ---------------------------------------------
>
>                 Key: TEZ-3418
>                 URL: https://issues.apache.org/jira/browse/TEZ-3418
>             Project: Apache Tez
>          Issue Type: Improvement
>          Components: UI
>    Affects Versions: 0.8.3
>         Environment: Tez 0.8.3, Hadoop 2.7.2
>            Reporter: Alexandre Linte
>
> Today it is not possible to use Tez UI/UI2 in a Kerberized cluster without 
> Ambari. 
> This feature request asks for an improvement of the Tez UI2 in order to fully 
> support Kerberos. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to