[jira] [Commented] (AMBARI-15316) Kerberos: Provide SHA256 or SHA512 options for template principal digest

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

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

Hadoop QA commented on AMBARI-15316:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12791790/AMBARI-15316_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 1 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/5757//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5757//console

This message is automatically generated.

> Kerberos: Provide SHA256 or SHA512 options for template principal digest
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-15316
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15316
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: active-directory, active_directory, kerberos
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15316_trunk_01.patch
>
>
> When generating accounts in an Active Directory, it may be useful to add a unique value to CN's.  In the past generating this value was done by taking the SHA1 hash of the relevant normalized principal name. For example {{ambari-qa-c1@EXAMPLE.COM}} yields {{d9b48cb1c075d3da9fab4855a4031266bab8fb6a}}.  
> Because using SHA1 at all may not be desirable, Ambari should provide options to use the following digest algorithms in the Active Directory account creation attribute template ({{kerberos-env/ad_create_attributes_template}}:
> ||Attribute Variables||Example||
> |$principal_digest|SHA1 hash of the $normalized_principal|
> |$principal_digest_256|SHA256 hash of the $normalized_principal|
> |$principal_digest_512|SHA512 hash of the $normalized_principal|
>    



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