[
https://issues.apache.org/jira/browse/AMBARI-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569447#comment-16569447
]
Robert Levas commented on AMBARI-21216:
---------------------------------------
[~yaolei]....
By default, I believe that this feature is turned off in Ambari 2.7. I have
plans to make it a more prominent feature in Ambari 3.0.
As for now, I think the only way to unlock the user is to use the Ambari REST
API. For Ambari 3.0, I hope to get the UI updated so that an Ambari
administrator can unlock the user via the user's _profile_ page. I did also
want to add a feature to unlock the user based on time... maybe after some
configured timeout. However due to time constraints and other priorities, I
have not been able to work on this feature. Hopefully we can get something done
in Ambari 3.0.
> Add support for consecutive login failure accounting
> ----------------------------------------------------
>
> Key: AMBARI-21216
> URL: https://issues.apache.org/jira/browse/AMBARI-21216
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-21216_branch-feature-AMBARI-20859_01.patch,
> AMBARI-21216_branch-feature-AMBARI-20859_02.patch,
> AMBARI-21216_branch-feature-AMBARI-20859_03.patch
>
>
> Add support for consecutive login failure accounting where as log-in failures
> should increment the {{users.consecutive_failures}} and successful
> authentication attempts should reset the value to 0.
> Concurrency should be kept in mind to handle simultaneous authentication
> attempts for the same user.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
