From issues-return-66070-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Tue Jan 30 16:58:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 4FB7918061A for ; Tue, 30 Jan 2018 16:58:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3F666160C53; Tue, 30 Jan 2018 15:58:04 +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 87955160C42 for ; Tue, 30 Jan 2018 16:58:03 +0100 (CET) Received: (qmail 27436 invoked by uid 500); 30 Jan 2018 15:58: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 27427 invoked by uid 99); 30 Jan 2018 15:58:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2018 15:58:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5B11318034D for ; Tue, 30 Jan 2018 15:58:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ltmfdfRu9fs7 for ; Tue, 30 Jan 2018 15:58:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id EEB865F3B5 for ; Tue, 30 Jan 2018 15:58: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 405A5E00FC for ; Tue, 30 Jan 2018 15:58: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 06DC221300 for ; Tue, 30 Jan 2018 15:58:00 +0000 (UTC) Date: Tue, 30 Jan 2018 15:58:00 +0000 (UTC) From: "Robert Levas (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-22876) Disable consecutive authentication failure account lockout feature by default 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-22876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-22876: ---------------------------------- Summary: Disable consecutive authentication failure account lockout feature by default (was: Disable account lockout feature by default) > Disable consecutive authentication failure account lockout feature by default > ----------------------------------------------------------------------------- > > Key: AMBARI-22876 > URL: https://issues.apache.org/jira/browse/AMBARI-22876 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.7.0 > Reporter: Robert Levas > Assignee: Robert Levas > Priority: Major > Labels: authentication > Fix For: 2.7.0 > > > Disable the account lockout feature by default. This feature locks an account after a configured number of failed authentication attempts. By defaulting \{{authentication.local.max.failures}} to \{{0}}, this feature will be disabled by default. > If enabled, a user account may be locked out due to number of authentication failures. There is a REST API call to unlock the user; however a user interface change will not be available until Ambari 3.x. -- This message was sent by Atlassian JIRA (v7.6.3#76005)