[jira] [Commented] (AMBARI-7780) Storm UI server should have the same default keytab value as of other components for spnego principal

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-7780:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12674881/AMBARI-7780.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/198//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/198//console

This message is automatically generated.

> Storm UI server should have the same default keytab value as of other components for spnego principal
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7780
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7780
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7780.patch
>
>
> The problem will occur when there are two different keytabs containing same principal on a host. In this scenario only one principal will be considered to be valid. (The reason is due to different kvno of the principal in both keytabs while using --randkey option to add principal to keytab)
> For example if Namenode host and Storm UI Server are co-hosted. 
> spnego.service.keytab will have principal HTTP/hostname@EXAMPLE.COM which will be used by NameNode web UI.
> Storm UI daemon will also try to authenticate with the same principal but from a different keytab path and with different kvno.
> In this scenario the keytab that was created last with the principal will hold valid principal and the other daemon will fail to authenticate with kerberos authentication error.



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