Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 80DE310A50 for ; Thu, 12 Feb 2015 12:18:13 +0000 (UTC) Received: (qmail 45189 invoked by uid 500); 12 Feb 2015 12:18:13 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 45161 invoked by uid 500); 12 Feb 2015 12:18:13 -0000 Mailing-List: contact dev-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 dev@ambari.apache.org Received: (qmail 44983 invoked by uid 99); 12 Feb 2015 12:18:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2015 12:18:13 +0000 Date: Thu, 12 Feb 2015 12:18:13 +0000 (UTC) From: "Vitaly Brodetskyi (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-9593) Kerberos: configs should include note and represent user MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi resolved AMBARI-9593. --------------------------------------- Resolution: Fixed Committed to trunk > Kerberos: configs should include note and represent user > -------------------------------------------------------- > > Key: AMBARI-9593 > URL: https://issues.apache.org/jira/browse/AMBARI-9593 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.0.0 > Reporter: Vitaly Brodetskyi > Assignee: Vitaly Brodetskyi > Priority: Critical > Fix For: 2.0.0 > > Attachments: AMBARI-9593.patch > > > When enabling kerberos, the configuration changes should use the user that is performing the action (not "kerberization") and the those configuration changes should include a note saying this change was made because of "Kerberos enabled" or "Kerberos disabled". > Enabling Kerberos on Cluster > Disabling Kerberos on Cluster -- This message was sent by Atlassian JIRA (v6.3.4#6332)