ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements
Date Fri, 14 Jul 2017 14:46:00 GMT

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

Hadoop QA commented on AMBARI-20861:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12877284/AMBARI-20861_branch-feature-AMBARI-20859_05.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11790//console

This message is automatically generated.

> BE: Extend Ambari REST API to Support User Account Management Improvements
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-20861
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20861
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: rest_api, security
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20861_branch-feature-AMBARI-20859_01.patch, AMBARI-20861_branch-feature-AMBARI-20859_02.patch,
AMBARI-20861_branch-feature-AMBARI-20859_04.patch, AMBARI-20861_branch-feature-AMBARI-20859_05.patch
>
>
> Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operations on the
authentication sources related to an Ambari user account.
> * * {{/api/v1/users/:USERNAME/sources}}
> ** List a user’s authentication sources
> ** Add a new authentication source for a user
> * {{/api/v1/users/:USERNAME/sources/:SOURCE_ID}}
> ** Get details on a specific authentication source for a user
> ** Modify details for a specific authentication source for a user
> Update the following entry points, ensuring backwards compatibility where possible:
> * {{/api/v1/users}}
> ** List all users
> ** Add a new user
> ** Backward compatibility: Set password should create or update the appropriate user_authentication
record. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message