Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5F8F9200C62 for ; Wed, 26 Apr 2017 17:25:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5E254160BB4; Wed, 26 Apr 2017 15:25:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A56E2160B95 for ; Wed, 26 Apr 2017 17:25:07 +0200 (CEST) Received: (qmail 96721 invoked by uid 500); 26 Apr 2017 15:25:06 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 96712 invoked by uid 99); 26 Apr 2017 15:25:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2017 15:25:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7CB8DD52A0 for ; Wed, 26 Apr 2017 15:25:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id o_FS2j2XUptm for ; Wed, 26 Apr 2017 15:25:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 994BA5F342 for ; Wed, 26 Apr 2017 15:25:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 35675E0BDF for ; Wed, 26 Apr 2017 15:25:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A007A21DE4 for ; Wed, 26 Apr 2017 15:25:04 +0000 (UTC) Date: Wed, 26 Apr 2017 15:25:04 +0000 (UTC) From: "Robert Levas (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-20861) BE: Extend Ambari REST API to Support User Account Management Improvements MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 26 Apr 2017 15:25:08 -0000 Robert Levas created AMBARI-20861: ------------------------------------- Summary: BE: Extend Ambari REST API to Support User Account Ma= nagement 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 Fix For: 3.0.0 Update the Ambari REST API to allow for GET, POST, PUT, and DELETE operatio= ns on the authentication sources related to an Ambari user account. Add the following entry points: * {{/api/v1/users/:USER_ID}} ** Get a user ** Modify a user * * {{/api/v1/users/:USERNAME/sources}} ** List a user=E2=80=99s 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 * {{/api/v1/users/:USER_ID/sources}} ** List a user=E2=80=99s authentication sources ** Add a new authentication source for a user * {{/api/v1/users/:USER_ID/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 p= ossible: * {{/api/v1/users}} ** List all users ** Add a new user ** Backward compatibility: Set password should create or update the appropr= iate user_authentication record.=20 -- This message was sent by Atlassian JIRA (v6.3.15#6346)