You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/05/01 10:27:05 UTC
[jira] [Commented] (AMBARI-10018) Kerberos: Password generator
needs to generate passwords based on rules to satisfy password policy
[ https://issues.apache.org/jira/browse/AMBARI-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522937#comment-14522937 ]
Hadoop QA commented on AMBARI-10018:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12729683/AMBARI-10018_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:red}-1 core tests{color}. The test build failed in ambari-server
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2594//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2594//console
This message is automatically generated.
> Kerberos: Password generator needs to generate passwords based on rules to satisfy password policy
> --------------------------------------------------------------------------------------------------
>
> Key: AMBARI-10018
> URL: https://issues.apache.org/jira/browse/AMBARI-10018
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.1.0
>
> Attachments: AMBARI-10018_01.patch
>
>
> The password generator used to generate passwords for identities needs to generate passwords based on a rule set rather than just a random sequence of characters.
> In a KDC (MIT or Active Directory), there may be a policy in place requiring a certain characteristics for the password. By creating a password consisting if 18 characters pulled randomly from {{abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890?.!$%^*()-_+=~}}, there is no guarantee that any specific policy will be met.
> The following rules should be settable:
> * Length
> * Minimum number of lowercase letters (a-z)
> * Minimum number of uppercase letters (A-Z)
> * Minimum number of digits (0-9)
> * Minimum number of punctuation characters ({{?.!$%^*()-_+=~}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)