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 B70CB200CBC for ; Tue, 20 Jun 2017 09:11:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B66A0160BEF; Tue, 20 Jun 2017 07:11:03 +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 0943D160BD3 for ; Tue, 20 Jun 2017 09:11:02 +0200 (CEST) Received: (qmail 5529 invoked by uid 500); 20 Jun 2017 07:11:02 -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 5518 invoked by uid 99); 20 Jun 2017 07:11:02 -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; Tue, 20 Jun 2017 07:11:02 +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 B580EC11DD for ; Tue, 20 Jun 2017 07:11:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.21 X-Spam-Level: X-Spam-Status: No, score=-99.21 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 ycCASG9bkKNS for ; Tue, 20 Jun 2017 07:11:01 +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 D0BA35F6C1 for ; Tue, 20 Jun 2017 07:11:00 +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 5AE93E0663 for ; Tue, 20 Jun 2017 07:11:00 +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 1186524005 for ; Tue, 20 Jun 2017 07:11:00 +0000 (UTC) Date: Tue, 20 Jun 2017 07:11:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21259) Need to use provided password when usersync sync source and authentication method are different MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 20 Jun 2017 07:11:03 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055250#comment-16055250 ] Hudson commented on AMBARI-21259: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7653 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7653/]) AMBARI-21259 Need to use provided password when usersync sync source and (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8df01a8f84f9b404be9248f36484baebc7de582f]) * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py > Need to use provided password when usersync sync source and authentication method are different > ----------------------------------------------------------------------------------------------- > > Key: AMBARI-21259 > URL: https://issues.apache.org/jira/browse/AMBARI-21259 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Reporter: Mugdha Varadkar > Assignee: Mugdha Varadkar > Fix For: 2.5.2 > > Attachments: AMBARI-21259.patch > > > In Ambari for Ranger, the password for user authentication is taken from Ranger User Info Tab for LDAP/AD when sync-source and authentication method is LDAP/AD. > For the scenario where sync-source and authentication method are different or when credentials for sync-source and authentication are different will need to take password from advanced section for LDAP/AD. -- This message was sent by Atlassian JIRA (v6.4.14#64029)