[
https://issues.apache.org/jira/browse/AMBARI-22876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22876:
----------------------------------
Status: Patch Available (was: Open)
> 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, pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Disable consecutive authentication failure 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)
