Bug 1041891 - [RFE][keystone]: Inadequate Account Lockout in Keystone
Summary: [RFE][keystone]: Inadequate Account Lockout in Keystone
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:55 UTC by RHOS Integration
Modified: 2015-03-19 16:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:52:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 19:55:15 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/lock-user.

Description:

It is currently not possible to define an account Lockout policy in Openstack/Keystone to lock a user account after a given number of failed login attempts. So this blueprint is to add a configurable policy to lock a user account after a given number of failed login attempts.

Details:
Keystone's SQL Identity backend must support locking out accounts after 
some number of invalid login attempts. This is a common feature among 
authentication systems and is a common requirement among deployers.

Currently, users (or exploiters) can attempt to authenticate to Keystone 
as often as they want with invalid passwords. This is a security problem 
because it allows an attacker to use a dictionary of passwords if they 
know (or can guess) a username.

Keystone should be configurable so that it rejects any authentication 
attempts for a user after some number of invalid login attempts.
Keystone should be configurable so that lockouts do not happen.
The number of invalid login attempts must be configurable.
There needs to be some way to unlock an account that's locked.
There needs to be some way to tell if a user's account is locked or not.
There should be a way to list all locked users.
There should be a way to reset the number of attempts for a user.
Keystone must not provide information to an attacker that the account is 
locked or not.
Account lockouts must work when there are multiple Keystone servers (as 
in, use the common DB).

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.