[
https://issues.apache.org/jira/browse/AMBARI-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993787#comment-15993787
]
Hadoop QA commented on AMBARI-20907:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12866026/AMBARI-20907_branch-feature-AMBARI-20859.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11568//console
This message is automatically generated.
> Create Database Schema for Improved User Account Management
> -----------------------------------------------------------
>
> Key: AMBARI-20907
> URL: https://issues.apache.org/jira/browse/AMBARI-20907
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20907_branch-feature-AMBARI-20859.patch
>
>
> User management tables in the DB should be:
> *{{users}}*
> ||Name||Type||Description||
> |user_id|INTEGER|Internal unique identifier|
> |principal_id|INTEGER|Foreign key from adminprincipal table|
> |user_name|VARCHAR|Unique, case-insensitive, login identifier expected to be
> used when logging into Ambari|
> |create_time|TIMESTAMP|Creation time for this account in Ambari|
> |active|BOOLEAN|Active/not active flag|
> |consecutive_failed_auth_attemps|INTEGER|The number a failed authorization
> attempts since the last successful authentication|
> |active_widgets_layout|VARCHAR| |
> |display_name|VARCHAR|Cosmetic name value to show the user in user interfaces|
> |local_username|VARCHAR|Case-sensitive username to use when impersonating
> user in facilities like Ambari Views|
> * Primary Key: {{user_id}}
> * Foreign Key: {{principal_id}} -> {{adminprincipal.principal_id}}
> *{{user_authentication}}*
> ||Name||Type||Description||
> |user_authentication_id|INTEGER|Primary key for this table|
> |user_id|INTEGER|Foreign key from users table|
> |authentication_type|VARCHAR|Type of authentication system - LOCAL, LDAP,
> KERBEROS, JTW, PAM, etc...
> |authentication_key|VARCHAR|Type-specific key (or identifier):
> * LOCAL: the user's password (digest)
> * LDAP: the user’s distinguished name
> * KERBEROS: the user’s principal
> * etc...|
> |create_time|TIMESTAMP|Creation time of this record
> |update_time|TIMESTAMP|Update time for this record, can be used to enforce
> password retention times|
> * Primary Key: {{user_authentication_id}}
> * Foreign Key: {{user_id}} -> {{users.user_id}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
