ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20907) Create Database Schema for Improved User Account Management
Date Thu, 18 Jan 2018 18:26:01 GMT

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

Hudson commented on AMBARI-20907:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/])
AMBARI-20907. Create Database Schema for Improved User Account (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7460cebf90e8f77b3b14457a64423ebc3ba028cc])
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql


> 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
>              Labels: user_management
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20907_branch-feature-AMBARI-20859.patch, AMBARI-20907_branch-feature-AMBARI-20859_02.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|
> |active|BOOLEAN|Active/not active flag|
> |consecutive_failures|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|
> |create_time|TIMESTAMP|Creation time for this account in Ambari|
> * 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
(v7.6.3#76005)

Mime
View raw message