[jira] [Commented] (AMBARI-18365) Add Ambari configuration options to support Kerberos token authentication

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

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

Hadoop QA commented on AMBARI-18365:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12828101/AMBARI-18365_trunk_01.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {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 ambari-server.

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

This message is automatically generated.

> Add Ambari configuration options to support Kerberos token authentication
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-18365
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18365
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: authentication, kerberos, security
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18365_branch-2.5_01.patch, AMBARI-18365_trunk_01.patch
>
>
> Add the followng Ambari configuration options to support Kerberos token authentication
> * {{authentication.kerberos.enabled}}
> ** Determines whether to use Kerberos (SPNEGO) authentication when connecting Ambari:  {{true}} to enable this feature; {{false}}, otherwise
> * {{authentication.kerberos.spnego.principal}}
> ** The Kerberos principal name to use when verifying user-supplied Kerberos tokens for authentication via SPNEGO
> * {{authentication.kerberos.spnego.keytab.file}}
> ** The Kerberos keytab file to use when verifying user-supplied Kerberos tokens for authentication via SPNEGO
> * {{authentication.kerberos.user.types}}
> ** A comma-delimited (ordered) list of preferred user types to use when finding the Ambari user account for the user-supplied Kerberos identity during authentication via SPNEGO
> * {{authentication.kerberos.auth_to_local.rules}}
> ** The auth-to-local rules set to use when translating a user's principal name to a local user name during authentication via SPNEGO.
> NOTE: These properties are in the {{ambari.properties}} file since this feature may be enabled whether the rest of the cluster has Kerberos enabled or not. 



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